Repository navigation

Issues

Comments regarding new MATF group note
w3c/matf#299 · opened on Sep 16, 2026
"Comments on Webviews and Web Content" draft section
w3c/matf#296 · opened on Aug 10, 2026 · Third Draft
WCAG2ICT v20251211 updates
w3c/matf#285 · opened on Jan 7, 2026 · Third Draft
5
EN 301 549 v4.1.0 updates
w3c/matf#284 · opened on Jan 7, 2026 · Third Draft
2
Proposal: Standardization of core accessibility roles and states for native mobile platforms
w3c/matf#283 · opened on Dec 28, 2025 · Third Draft
3
Pointer input note
w3c/matf#282 · opened on Dec 1, 2025
1
How does SC 2.1.1 apply to long-press?
w3c/matf#275 · opened on Oct 15, 2025 · Third Draft
1
Update success criteria with normative text
w3c/matf#271 · opened on Sep 12, 2025 · Third Draft
5
SUB - 4.1.2 - Dealing with semantic structures not corresponding to native app capabilities
Task
w3c/matf#264 · opened on Sep 4, 2025 · Third Draft
Update timeline for WCAG2Mobile
w3c/matf#261 · opened on Aug 18, 2025 · Third Draft
Research: text sizes and dp/pt comparison with CSS px
w3c/matf#260 · opened on Aug 18, 2025 · Third Draft
8
SUB - make a decision on system settings as sufficient techniques
Task
w3c/matf#241 · opened on Jul 8, 2025
SUB - review the WCAG2ICT key term "accessibility services of platform software"
Task
w3c/matf#232 · opened on Jul 8, 2025 · Third Draft
SUB - 2.4.7 - Focus Visible - Draft SC text (keep this SC as written with potential note)
Task
w3c/matf#219 · opened on Jun 25, 2025
SUB - 1.3.1 - Info and Relationships - Add note about custom accessibility actions
Task
w3c/matf#216 · opened on Jun 18, 2025 · Third Draft
SUB - 2.4.7 - Focus Visible - Add second note: 'Not all mobile platforms provide a way to programmatically change the keyboard focus indicator.'
Task
w3c/matf#208 · opened on Jun 18, 2025
SUB - 1.4.11 - Non-text Contrast - Note "if you have the ability to change the appearance to reach minimum contrast, then do it"
Task
w3c/matf#207 · opened on Jun 18, 2025
1
SUB - 1.4.11 - Non-text Contrast - Determine potential note to cover best-practices for user agent determined appearance and inactive components
Task
w3c/matf#206 · opened on Jun 18, 2025
SUB - 1.4.11 - Non-text Contrast - Consider addressing hover/focus states
Task
w3c/matf#205 · opened on Jun 18, 2025
SUB - 1.4.11 - Non-text Contrast - Consider note about customizing the focus indicator
Task
w3c/matf#204 · opened on Jun 18, 2025
SUB - 1.4.11 - Non-text Contrast - Consider Dark Mode in the bigger note about respecting system settings
Task
w3c/matf#203 · opened on Jun 18, 2025
SUB - 4.1.2 - Name, Role, Value - Research what happens if your "standard user interface component" meet 4.1.2 when used according to specification
Task
w3c/matf#201 · opened on Jun 18, 2025 · Third Draft
SUB - 4.1.2 - Name, Role, Value - Add note about custom actions
Task
w3c/matf#200 · opened on Jun 18, 2025 · Third Draft
SUB - 4.1.2 - Name, Role, Value - Draft proposed language for a note about roles and states for 4.1.2
Task
w3c/matf#199 · opened on Jun 18, 2025 · Third Draft
SUB - 3.2.1 - On Focus - Feedback from WCAG on user interface component (control) vs component (element?)
Task
w3c/matf#194 · opened on Jun 18, 2025