Skip to content

Add Accessibility considerations section #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 30, 2025
Merged

Add Accessibility considerations section #117

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e88061
Add Accessibility considerations section
marcoscaceres Sep 3, 2025
addd694
fix xrefs
marcoscaceres Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
67 changes: 60 additions & 7 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ <h2>
</p>
</section>
<section id="presentation">
<h2>
<h2 id="displaying-a-badge">
Displaying a badge
</h2>
<p>
Expand Down Expand Up @@ -386,12 +386,65 @@ <h2>
system load, user preferences, and accessibility considerations.
</p>
</section>
<section class="informative">
<h2>
Accessibility considerations
</h2>
<div class="issue" data-number="24"></div>
</section>
<h2>
Accessibility considerations
</h2>
<p>
Application badges convey status that can require the user's attention.
Because badges are often presented outside the web content area (for
example, on an app icon in the dock), user agents need to ensure that the
information remains accessible and controllable through platform
accessibility features and user preferences.
</p>
<h3>
Screen reader compatibility
</h3>
<p>
User agents SHOULD expose the current [=badge/value=] (including
[=badge/"flag"=] vs. [=badge/number=]) through platform accessibility
APIs so that assistive technologies can present it on demand (for
example, when the user focuses the application icon).
</p>
<p>
User agents <em>SHOULD NOT</em> automatically announce badge changes;
instead, they SHOULD follow platform conventions that avoid unsolicited
interruptions.
</p>
<h3 class="informative">
Visual accessibility
</h3>
<p>
Comment on lines +389 to +416
Copy link
Preview

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section opening tag on line 389 is removed but the section is not properly closed in the new structure. The accessibility considerations content should be wrapped in a proper section element to maintain semantic HTML structure.

Copilot uses AI. Check for mistakes.

As badges are typically drawn by the underlying platform, visual
affordances are typically handled there. Nevertheless, user agents and
platforms need to consider:
</p>
<ul>
<li>Do not rely on color alone to convey meaning (provide text or an
accessible name).
</li>
<li>Ensure sufficient non-text contrast between badge glyph and
background.
</li>
<li>Use sizing that remains legible across system font/scale settings.
</li>
<li>Honor high-contrast / forced-colors and dark mode preferences where
applicable.
</li>
<li>If animating badge changes, honor reduced-motion preferences and
avoid flashing effects.
</li>
</ul>
<h3>
Platform integration and user preferences
</h3>
<p>
User agents SHOULD integrate with platform accessibility settings and
themes.
</p>
<p>
User agents SHOULD reflect OS-level per-application badge preferences
(for example, when the operating system disables badges for an app).
</p>
<section id="conformance"></section>
</body>
</html>
Loading