Course Preview

Web Accessibility

Web accessibility is the practice of designing and building websites so people with disabilities can perceive, understand, navigate, and operate them. It connects content, semantic HTML, keyboard behavior, visual presentation, media alternatives, browsers, and assistive technologies.

itWeb development | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic: Web Accessibility

Web accessibility is the discipline of keeping a website usable when a person does not see, hear, point, read, or move in the way its author happened to expect. This is less mystical than it sounds. It means the visible interface and the browser's other description of that interface must agree. If they disagree, the page has developed two personalities, and neither is much help.

The useful mental model is a delivery path. Content and design express an intention. HTML, CSS, and JavaScript turn it into structure, appearance, and behavior. The browser renders it and builds an accessibility tree, which assistive technology uses to present and operate the page. A fault near the beginning gets a remarkably reliable lift through every later layer. An unnamed icon button can look polished while arriving as an unnamed button to a screen reader. It has not become mysterious. It has merely lost its name on the journey.

WCAG supplies the shared map: perceivable, operable, understandable, and robust. The labels are less important than the questions behind them. Can information reach a person in another form? Can every function work without a pointer? Are labels, instructions, and errors clear? Can browsers and assistive technology interpret the meaning? Level AA covers applicable Level A and AA criteria, but a conforming-looking component is not a complete process. The payment dialog still counts.

Start with native HTML. A real button brings focus and expected keyboard activation, while a generic element with a button role brings a very polite list of work you now owe. ARIA can add semantics when HTML cannot express a custom interaction. It does not add the interaction itself. Names, roles, states, and visible behavior must move together.

No scanner can settle the whole matter. Inspect semantics, operate the task with a keyboard, change zoom and reflow settings, check supported screen-reader combinations, and involve people with disabilities. The Cheatsheet keeps the compact rules close. The Reference tab leads to the standards and patterns. The Quiz checks the distinctions that tend to go missing during a hurried release. The practice exercise turns the model into a small, inspectable task. That is plenty of work for one page. The page, regrettably, has opinions about it.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources