Skip to content

Module. 8.Test Questions.md

Latest commit

 

History

History
137 lines (82 loc) · 4.99 KB

Module. 8.Test Questions.md

File metadata and controls

137 lines (82 loc) · 4.99 KB

🧠 Test Questions & Brain Teasers: Accessibility Best Practices

🧪 Advanced Test Questions

These questions are designed to test your theoretical knowledge, practical understanding, and ability to apply accessibility concepts in real-world documentation scenarios.

📍 Multiple Choice (Select the most correct answer)

  1. Which of the following HTML practices best supports screen reader accessibility?

    A. Using <div> elements with inline styles B. Nesting <h1> tags inside paragraphs C. Using semantic tags like <nav>, <article>, and <aside> D. Adding alt="" to all decorative images

  2. In WCAG 2.2, which of the following is NOT a core principle?

    A. Perceivable B. Understandable C. Adjustable D. Robust

  3. When designing accessible tables for documentation, which of the following is NOT a recommended practice?

    A. Using <th> for headers B. Adding scope attributes to header cells C. Including merged cells for visual hierarchy D. Including captions and summaries

  4. Which scenario best represents a WCAG violation in a document?

    A. Color contrast of 5:1 between text and background B. Descriptive headings organized using H1 → H3 hierarchy C. A tooltip that can only be triggered by hovering with a mouse D. A chart described in both alt text and a footnote

🧠 Short Answer Questions

  1. Explain how semantic HTML improves accessibility for screen reader users. Provide examples.

  2. Describe how plain language contributes to the “Understandable” principle of WCAG. How would you enforce this in a cross-functional team?

  3. You’re writing a documentation set for a financial platform. How would you ensure that visually impaired users can understand a complex pie chart comparing monthly expenses?

  4. What is the relationship between keyboard navigation and cognitive load in accessible documents?

🔍 Scenario-Based Challenges

  1. Scenario: A documentation portal for a government service uses colored buttons (green for “Accept,” red for “Decline”) with no accompanying text labels.

    Question: Identify at least 3 accessibility violations present in this setup and propose compliant design alternatives.

  2. Scenario: Your product team insists on embedding video tutorials without transcripts in the onboarding documentation to "keep it visual."

    Question: Craft a strong accessibility-oriented argument (with standards references) against this practice and offer an alternative workflow.

🧠 Brain Teasers

These questions are not just about right or wrong—they push your reasoning and creativity in solving accessibility challenges.

  1. Accessibility Paradox

"Removing a keyboard trap makes your site more accessible, but can introduce security issues on login forms." Question: How would you resolve this conflict while remaining WCAG-compliant?

  1. Color Dependency Thought Experiment You’ve designed a multi-step instructional guide using only blue arrows and green checkmarks to indicate completed steps.

Question: Without using colors or reworking the layout entirely, how can you make the document accessible to people with Deuteranopia (red-green color blindness)?

  1. The Font Size Dilemma The design system your team uses has a fixed font size of 13px. Accessibility guidelines recommend at least 16px for body text.

Question: How would you approach this conflict between design fidelity and accessibility compliance in your documentation system?

  1. Glitch in the AI An automated accessibility checker (e.g., Axe) shows “no issues,” but a screen reader user complains they can’t access dropdown content.

Question: Why might this happen, and what manual test(s) would you perform to uncover the issue?

  1. Case Study Simulation Imagine you're auditing a 50-page API documentation site. The site has headings in all caps (GETTING STARTED, AUTHORIZATION, etc.), inconsistent use of ARIA roles, and complex terminology without a glossary.

Question: List at least five steps you would take to bring this documentation set into full accessibility compliance, referencing specific WCAG principles.

📝 Bonus: Documentation Rewrite Challenge

Rewrite the following example to meet accessibility and plain language guidelines:

"Initiate authentication by utilizing your pre-established credentials via the designated login interface. Upon successful verification, proceed to the application dashboard."

Accessibility Rewrite Example:

"Log in using your username and password. Once verified, you’ll be directed to your dashboard."

🎯 Scoring & Evaluation

  • Multiple Choice: 5 points each
  • Short Answers: 10 points each
  • Scenario-Based: 15 points each
  • Brain Teasers: 20 points each (creativity, standards references, empathy)
  • Rewrite Challenge: 15 points (clarity, tone, and conformance to guidelines)