BAD Demo Design Update/Requirements Analysis

From Education & Outreach

Key links

This page has been replaced by BAD Demo Update Requirements Analysis

Purpose/Goal

Make BAD demo more attractive to designers of websites and apps, by modernizing visual design of demo, and recoding using responsive design techniques. Most common feedback about this resource: "This is such a useful resource, but the design is so outdated that it's hard to get people to use it."

Audiences, use cases

  • Primary audience:
    • Web developers and app developers looking for examples of barriers and accessibility solutions, to help build a practical understanding of design problems.
  • Secondary audiences:
    • Managers in need of orientation as to what an evaluation report should include, and examples of prioritization of repairs that a report might help them pursue.
    • Evaluators who may want to learn and/or test their own expertise against a well-vetted review.

Use cases

  • Web and/or app developer, new to accessibility, wanting an overview of design issues and how those can be addressed
  • Accessibility evaluator, some experience in testing, wanting to confirm whether they are identifying all of the conformance errors on a page
  • Accessibility evaluator, wanting to learn a more formal reporting method

Objectives, Tasks

  • Update visual design
    • Get estimates on responsive re-design
    • Develop plan for graphic redesign of BAD demo
  • Recode with responsive design techniques
    • Complete updated assessment of cross-platform compatibility
    • Integrate accessibility feature demonstrations of WAI-ARIA
    • Add WAI-ARIA attributes to framework and content (readiness for responsive design)
    • Prepare cross-linking plan to integrate BAD into future update of “Techniques for WCAG 2.0” and “Understanding WCAG 2.0”
    • Evaluate readiness of linking into WAI-DEV videos
    • Add specific BAD content related to assessment and remediation in mobile contexts, using latest proposed mobile accessibility guidance from current WCAG 2.0 extension-track work
    • Assess additional cross-linking opportunities within BAD and between related WCAG 2.0 support materials, including for query-based search readiness

Next steps

  1. EOWG review of requirements
  2. Develop new design
  3. Recode with responsive design techniques to the extent possible

Support

WCAG TA Project, Task 3

Notes

@@@@

Issues

The need to display large amounts of annotated content in the demo may make full responsive design challenging.