This was like a town hall hosted by W3C Web Accessibility Initiative (WAI – pronounced Way) during M-enabling. The goal was to talk about web accessibility and hear from attendees. This is not a comprehensive list but is a summary of what was discussed during this session.
- Discussion Topics: We talked about recent web accessibility updates and standards. Key topics included language transitions, making content more accessible for screen readers, and the role of authoring tools and browsers in fixing accessibility issues.
- Prioritizing Accessibility: The presenters stressed the importance of prioritizing work and focusing on quick wins to make the web more accessible.
- Highlighting Key Initiatives: We talked about WCAG 2 ICT Version, AI and accessibility research, and monthly updates on accessibility activities and publications.
- Challenges Discussed: Attendees discussed challenges like mobile accessibility, measuring accessibility maturity, and evaluating success criteria.
- WCAG 3 Development: The session touched upon the ongoing development of WCAG 3 and the need to explore short-term solutions as version 3 will take some time to finalize.
- Prioritization Challenges: Prioritizing accessibility issues isn’t one-size-fits-all; it depends on context and user needs. We also discussed the difficulty of comparing issues with different impacts. Something that isn’t necessary for a blind person using a screen reader (like large checkbox size) is critical for someone with fine motor control issues.
- Community Involvement: The presenters emphasized the need for community input and involvement in shaping W3C Web Accessibility Initiative’s vision and strategy.
- How to Get Involved: The presenters provided information on how attendees can participate, review drafts, and contribute technical editing expertise.
- Collaboration: We talked about the importance of collaborating with entities like the U.S. federal government and international regions for standards harmonization.
- Resource Challenges: We discussed the challenges of spreading resources thin and highlighted ongoing work with AXA and European standard EN D01549.
- Policy Development: The presenters mentioned the cautious approach to policy development and the importance of prioritizing relationships.
- Documentation: There was a suggestion to create separate sections for compliance, bad practices, and good-to-have recommendations in the organization’s documentation.
- Closing Remarks: In conclusion, attendees were invited to explore the WAVE website, sign up for updates, and review the draft mission and vision objectives.
Some Items for Consideration from the Session
- The challenges faced by non-coders in using authoring tools was brought up. This highlights the need for clear guidelines and support for individuals who are not familiar with coding.
- The lack of audio description in social media content is brought up as a concern. This emphasizes the importance of making online content accessible to individuals with visual impairments.
- The discussion on AI and automated testing raises questions about the future of accessibility testing and the potential benefits of using AI in this process with the understanding that AI cannot replace human manual testing.
- The need for better support for apps like YouTube in terms of accessibility highlights the importance of making digital platforms inclusive for all users.
- The monthly update on accessibility activities and publications provides valuable information for staying updated.
- The discussion on language transitions highlights the need for smoother experiences for screen reader users.
- The conversation on prioritizing work and focusing on quick wins shows the importance of practical solutions in improving accessibility.
- The challenges of measuring accessibility in different parts of an organization and integrating accessibility standards into policy and compliance.
- The importance of cultural accessibility maturity in organizations.