Add ARIA landmarks, live regions, and semantic HTML for screen reader accessibility #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements WCAG 2.1 AA accessibility improvements for screen readers and dynamic content announcements.
Changes
Screen Reader Navigation
<main>,<nav role="navigation">,role="search"<header>,<article>,<section>replacing generic divsaria-labelattributes on all interactive elementsForm & Input Accessibility
aria-requiredon required fieldsaria-describedbyfor contextual field help.sr-onlyaria-hidden="true"Dynamic Content Handling
aria-live="polite"for status updates (search results, product counts)aria-live="assertive"for errors and alertsData Table Semantics
scope="col"andscope="row"attributes on headers<caption>elements for table context<th>usage for row/column headersExample
Before:
After:
Security
Fixed XSS vulnerabilities in new ARIA attributes by using HTML-escaped output (
<%=vs<%-) for user-controlled content in alt text and aria-labels.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.