Reviewing a community conference programme

Scenario

A community conference team is preparing to publish its programme. You have been asked to review whether screen-reader users can understand the programme and its schedule table, choose sessions using its content and controls, follow multilingual information, inspect session details, and return without losing their place.

Your role: Accessibility tester reviewing a conference programme before publication

What you will practise

• Define a reproducible screen-reader review environment and scope.
• Navigate a programme by structure and links rather than relying on visual layout.
• Navigate the programme schedule and assess its table name and row-and-column relationships.
• Assess whether common controls expose useful names, roles, states, and keyboard behavior.
• Evaluate whether images, icons, and SVG controls communicate equivalent content and purpose.
• Separate language-markup failures from unavailable voices or platform support.
• Test modal naming, containment, background inertness, closing behavior, and focus restoration within a realistic task.
• Consolidate overlapping evidence and make a concise publication recommendation.

Methods used

• Testing page structure and links with a screen reader

  Check whether a page title, landmarks, and headings communicate useful structure and links make sense outside their surrounding text.

• Testing data tables with a screen reader

  Check whether a data table exposes a useful name, dimensions, navigation, and row-and-column relationships.

• Testing controls with a screen reader

  Check whether common controls expose useful names, roles, states, values, keyboard behavior, and changes after interaction.

• Testing image alternative text

  Decide what each image contributes in context and test whether its alternative communicates the same relevant purpose.

• Testing icons and SVGs with a screen reader

  Determine whether meaningful graphics have useful names and decorative graphics remain silent.

• Testing language changes with a screen reader

  Check whether content in another language triggers appropriate pronunciation without redundant language markup.

• Testing modal dialogs

  Test modal names, initial focus, keyboard containment, background inertness, closing behavior, and focus restoration.

Optional preparation

• Learning path

  Practical screen-reader testing

  Learn focused screen-reader techniques through guided methods and independent Exercises for structure, data tables, controls, images, graphics, language changes, and modal dialogs.

  Level: beginner

  Estimated time: 320 minutes

Review stages

1. Define the review conditions

   Record the workspace route, screen reader, browser, operating system, versions, installed voices, theme, viewport, initial UI state, and test scope. State what is outside the review.

2. Find your way through the programme

   Locate the keynote and selected sessions using heading navigation, sequential reading, link lists, and the at-a-glance schedule. Record the schedule name and navigate representative cells to assess whether its time, day, and room relationships are exposed. Check whether programme structure and session destinations remain understandable outside the visual layout.

   Use:

   • Testing page structure and links with a screen reader
   • Testing data tables with a screen reader

3. Choose a session using its complete content

   Identify speakers and venues, compare graphical information with nearby text, and try the graphical schedule control. Check its name, role, keyboard operation, and exposed state, then decide which graphics communicate information or function and which should remain silent.

   Use:

   • Testing controls with a screen reader
   • Testing image alternative text
   • Testing icons and SVGs with a screen reader
   • Testing page structure and links with a screen reader

4. Review multilingual session information

   Read the Finnish and Swedish content. Distinguish markup problems from unavailable voices or unsupported automatic switching, and record the environment needed to reproduce the result.

   Use:

   • Testing language changes with a screen reader

5. Inspect session details and return to the programme

   Check the names, roles, and operation of controls that open and close session details. Identify the dialog, navigate within it, attempt to reach background content, close it using supported methods, and continue from the trigger.

   Use:

   • Testing controls with a screen reader
   • Testing modal dialogs
   • Testing page structure and links with a screen reader
   • Testing icons and SVGs with a screen reader

6. Consolidate and recommend

   Merge overlapping evidence, distinguish defects from passing comparisons and support limitations, prioritize user impact, and recommend whether the programme is ready to publish.

   Use:

   • Testing page structure and links with a screen reader
   • Testing data tables with a screen reader
   • Testing controls with a screen reader
   • Testing image alternative text
   • Testing icons and SVGs with a screen reader
   • Testing language changes with a screen reader
   • Testing modal dialogs

Deliverables

• Test environment and review scope.
• Programme-navigation record.
• Findings with reproduction steps, evidence, user impact, and remediation direction.
• Passing checks and support-dependent observations.
• Concise publication recommendation identifying blockers and follow-up testing.