Skip to content

A little look inside.

This is a fictional report. Explore the findings to see how your next steps could look.

Request testing

Accessibility conformance report · Final report · 61 of 61 test conditions recorded

Example Studio website

Example Studio · Release 2026.09 · September 10, 2026

findings to address
6
not tested
1
conditions met
28

1.Summary of results

Counted from the recorded results. Conditions that do not apply are left out of the total.

Section 508 · Trusted Tester v.5.1.3

28 of 34 applicable conditions met

  • 28 met
  • 5 not met
  • 1 not tested
  • 27 do not apply

Disability impact

How many failing test conditions affect each functional performance criterion. Counted over conditions, so one condition with several defects counts once.

  • Vision 12
  • Hearing 0
  • Speech 0
  • Manipulation and strength 2
  • Language, cognitive and learning 0
  • Photosensitivity 0

2.Findings to address

Showing 6 of 6 findings. Expand a finding for what was seen, the expected behavior and the next action.

4.A All tested pages · Main menu 2.1.1

The menu trigger is a clickable div. Tab skips it, so the navigation links cannot be reached with a keyboard. The header with keyboard focus on the logo link, then on the search button: the menu trigger between them never receives focus.

4.A All tested pages · Main menu, after activating a link 2.1.1

The menu stays open after its last link is activated, so focus is left inside a menu that no longer describes where the user is.

4.F Services page · Enquiry dialog 2.4.3

Tab moves out of the open enquiry dialog and into the page behind it, so the focus order no longer matches the task on screen. Screen recording of tabbing past the last control in the enquiry dialog and landing on a background link.

5.F Contact page · Required fields 3.3.1

An empty required field is marked only by a change of border colour. Nothing identifies the field in error in text.

7.A Header · Search button 1.1.1, 4.1.2

The search button contains only a decorative SVG, so its accessible name is empty.

13.A Contact page · Required fields 1.4.1

Colour is the only signal that a field is in error. The submitted contact form in greyscale, where the invalid email field is indistinguishable from the valid fields.

3.Results by requirement

Every test condition with its recorded result. Failed and not-tested results carry the tester’s note.

  • Pass
  • Fail
  • Does not apply
  • Not tested
  • 1.A Alt-version-conformant Criteria ID Conf. Req 1 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 1.B Alt-version-equivalent Criteria ID Conf. Req 1 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 1.C Alt-version-access Criteria ID Conf. Req 1 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 1.D Non-interference Criteria ID Conf. Req 5 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 2.A 1.4.2-Audio-control Criteria ID 1.4.2, Conf. Req 5· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 2.B 2.2.2-Blinking-moving-scrolling Criteria ID 2.2.2, Conf. Req 5· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 2.C 2.2.2-Auto-updating Criteria ID 2.2.2, Conf. Req 5· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 2.D 4.1.2-change-notify-auto Criteria ID 4.1.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 3.A 2.3.1-flashing Criteria ID 2.3.1, Conf. Req 5· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply

    Issue 1

    No flashing content was found on the tested pages.

  • 4.A 2.1.1-keyboard-access Criteria ID 2.1.1· Level A HomeFailServicesFailContactFail

    Issue 1 Global issue

    The menu trigger is a clickable div. Tab skips it, so the navigation links cannot be reached with a keyboard. The header with keyboard focus on the logo link, then on the search button: the menu trigger between them never receives focus.

    Location / screen
    All tested pages · Main menu
    Remediation details
    Use a native button for the menu trigger. Keep its expanded state in sync with the menu and make sure the revealed links are reachable.

    Additional issue 2 Global issue

    The menu stays open after its last link is activated, so focus is left inside a menu that no longer describes where the user is.

    Location / screen
    All tested pages · Main menu, after activating a link
    Remediation details
    After navigation, close the menu, update the expanded state, and place focus at the destination heading when navigation happens without a page reload.
  • 4.B 2.1.1-no-keystroke-timing Criteria ID 2.1.1· Level A HomePassServicesPassContactPass
  • 4.C 2.1.2-no-keyboard-trap Criteria ID 2.1.2, Conf. Req 5· Level A HomePassServicesPassContactPass
  • 4.D 2.4.7-focus-visible Criteria ID 2.4.7· Level AA HomePassServicesPassContactPass
  • 4.E 3.2.1-on-focus Criteria ID 3.2.1· Level A HomePassServicesPassContactPass
  • 4.F 2.4.3-focus-order-meaning Criteria ID 2.4.3· Level A HomePassServicesPassContactPass

    Issue 1

    Tab moves out of the open enquiry dialog and into the page behind it, so the focus order no longer matches the task on screen. Screen recording of tabbing past the last control in the enquiry dialog and landing on a background link.

    Location / screen
    Services page · Enquiry dialog
    Remediation details
    Use a native modal dialog or a tested accessible dialog component. Set initial focus and restore it to the opener after closing.
  • 5.A 3.3.2-label-provided Criteria ID 3.3.2· Level A HomePassServicesPassContactPass
  • 5.B 2.4.6-label-descriptive Criteria ID 2.4.6· Level AA HomePassServicesPassContactPass
  • 5.C 1.3.1-programmatic-label Criteria ID 1.3.1, 4.1.2· Level A HomePassServicesPassContactPass
  • 5.D 3.2.2-on-input Criteria ID 3.2.2· Level A HomePassServicesPassContactPass
  • 5.F 3.3.1-error-identification Criteria ID 3.3.1· Level A HomePassServicesPassContactPass

    Issue 1

    An empty required field is marked only by a change of border colour. Nothing identifies the field in error in text.

    Location / screen
    Contact page · Required fields
    Remediation details
    Add a visible error message and associate it with the input. Keep the color as an additional cue.
  • 5.G 3.3.3-error-suggestion Criteria ID 3.3.3· Level AA HomePassServicesPassContactPass
  • 5.H 3.3.4-error-prevention Criteria ID 3.3.4· Level AA HomePassServicesPassContactPass
  • 6.A 2.4.4-link-purpose Criteria ID 2.4.4, 4.1.2· Level A HomePassServicesPassContactPass
  • 7.A 1.1.1-meaningful-image-name Criteria ID 1.1.1, 4.1.2· Level A HomeFailServicesFailContactFail

    Issue 1 Global issue

    The search button contains only a decorative SVG, so its accessible name is empty.

    Location / screen
    Header · Search button
    Remediation details
    Give the button a concise name that describes its action. Keep the decorative icon hidden from assistive technology.
  • 7.B 1.1.1-decorative-image Criteria ID 1.1.1, 4.1.2· Level A HomePassServicesPassContactPass
  • 7.C 1.1.1-decorative-background-image Criteria ID 1.1.1, 4.1.2· Level A HomePassServicesPassContactPass
  • 7.D 1.1.1-captcha-alternative Criteria ID 1.1.1, 4.1.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 7.E 1.4.5-image-of-text Criteria ID 1.4.5· Level AA HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 8.A 2.2.1-timing-adjustable Criteria ID 2.2.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 9.A 2.4.1-bypass-function Criteria ID 2.4.1· Level A HomePassServicesPassContactPass
  • 9.B 3.2.3-consistent- navigation Criteria ID 3.2.3· Level AA HomePassServicesPassContactPass
  • 9.C 3.2.4-consistent-identification Criteria ID 3.2.4· Level AA HomePassServicesPassContactPass
  • 10.A 2.4.6-heading-purpose Criteria ID 2.4.6· Level AA HomePassServicesPassContactPass
  • 10.B 1.3.1-heading-determinable Criteria ID 1.3.1· Level A HomePassServicesPassContactPass
  • 10.C 1.3.1-heading-level Criteria ID 1.3.1· Level A HomePassServicesPassContactPass
  • 10.D 1.3.1-list-type Criteria ID 1.3.1· Level A HomePassServicesPassContactPass
  • 11.A 3.1.1-page-language-defined Criteria ID 3.1.1· Level A HomePassServicesPassContactPass
  • 11.B 3.1.2-part-language-defined Criteria ID 3.1.2· Level A HomePassServicesPassContactPass
  • 12.A 2.4.2-page-title-defined Criteria ID 2.4.2· Level A HomePassServicesPassContactPass
  • 12.B 2.4.2-page-title-purpose Criteria ID 2.4.2· Level A HomePassServicesPassContactPass
  • 12.C 4.1.2-frame-title Criteria ID 4.1.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 12.D 4.1.2-iframe-name Criteria ID 4.1.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 13.A 1.4.1-color-meaning Criteria ID 1.4.1· Level A HomePassServicesPassContactPass

    Issue 1

    Colour is the only signal that a field is in error. The submitted contact form in greyscale, where the invalid email field is indistinguishable from the valid fields.

    Location / screen
    Contact page · Required fields
    Remediation details
    Add a visible error message and associate it with the input. Keep the color as an additional cue.
  • 13.B 1.3.3-sensory-info Criteria ID 1.3.3· Level A HomePassServicesPassContactPass
  • 13.C 1.4.3-contrast Criteria ID 1.4.3· Level AA HomePassServicesPassContactPass
  • 14.A 1.3.1-table-identification Criteria ID 1.3.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 14.B 1.3.1-cell-header-association Criteria ID 1.3.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 14.C 1.3.1-layout-table-structure Criteria ID 1.3.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 15.A 1.3.2-content-order-meaning-css-position Criteria ID 1.3.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 16.A 1.2.1-audio-transcript-text Criteria ID 1.2.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 16.B 1.2.1-video- alternative-equivalent Criteria ID 1.2.1· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.A 1.2.2-captions-equivalent Criteria ID 1.2.2· Level A HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.B 1.2.5-audio-description-equivalent Criteria ID 1.2.5· Level AA HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.C 1.2.4-captions-live-equivalent Criteria ID 1.2.4· Level AA HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.D 503.4-caption-controls Criteria ID 503.4 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.E 503.4-description-controls Criteria ID 503.4.1 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.F 503.4.1-caption-control Criteria ID 503.4.2 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 17.G 503.4.2-description-control Criteria ID 503.4.2 HomeDoes not applyServicesDoes not applyContactDoes not apply
  • 18.A 1.4.4-resize-text Criteria ID 1.4.4· Level AA HomePassServicesPassContactPass
  • 19.A 2.4.5-multiple-ways Criteria ID 2.4.5· Level AA HomePassServicesPassContactPass
  • 20.A 4.1.1-parsing Criteria ID 4.1.1· Level A HomeNot testedServicesNot testedContactNot tested

    Issue 1

    No approved tool exists for this requirement, so the test process records it as not tested.

4.How the audit was run

What was tested, where, and what the results do not cover.

Test method
Trusted Tester v.5.1.3
Tested by
Easeweb · Sample Tester · Trusted Tester ID TT-0000-0000
Tester's email address
[email protected]
Review date
September 10, 2026
Browsers
Chrome 129, Safari 18, NVDA 2024.4, VoiceOver
Operating systems
Windows 11 23H2, macOS 15
Browser compatibility view
None
Product name
Example Studio website · Release 2026.09
Product type
Custom developed web page
Testing scope
Three pages chosen to cover every page layout on the site, the only form, and the one dialog: a content page, a page of repeated cards, and the contact form. Findings from them are expected to recur on the pages sharing those layouts.
Description
This sample covers three pages and identifies six findings across five test conditions. Start with the navigation and inquiry form so visitors can reach content and complete their tasks.

Fictional demonstration data. The tester, the Trusted Tester ID, the test environment, and the sampling plan shown here are illustrative. Issue resolution is not a compliance score.

5.Conformance by success criterion

The formal record by success criterion, as SCRT reports it.

Supports
Every test condition measuring this criterion passed.
Does not support
At least one test condition measuring this criterion failed.
Not applicable
This criterion does not apply to the product as tested.
Not evaluated
This criterion was not tested, so no result is claimed.
Criteria IDConformance levelRemarks and explanations
Conf. Req 1Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
Conf. Req 5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.4.2, Conf. Req 5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
2.2.2, Conf. Req 5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
4.1.2Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
2.3.1, Conf. Req 5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
2.1.1Does not supportThe menu trigger is a clickable div. Tab skips it, so the navigation links cannot be reached with a keyboard. The header with keyboard focus on the logo link, then on the search button: the menu trigger between them never receives focus. The menu stays open after its last link is activated, so focus is left inside a menu that no longer describes where the user is.The menu trigger is a clickable div. Tab skips it, so the navigation links cannot be reached with a keyboard. The header with keyboard focus on the logo link, then on the search button: the menu trigger between them never receives focus. The menu stays open after its last link is activated, so focus is left inside a menu that no longer describes where the user is.
2.1.2, Conf. Req 5Supports
2.4.7Supports
3.2.1Supports
2.4.3Does not supportTab moves out of the open enquiry dialog and into the page behind it, so the focus order no longer matches the task on screen. Screen recording of tabbing past the last control in the enquiry dialog and landing on a background link.Tab moves out of the open enquiry dialog and into the page behind it, so the focus order no longer matches the task on screen. Screen recording of tabbing past the last control in the enquiry dialog and landing on a background link.
3.3.2Supports
2.4.6Supports
1.3.1, 4.1.2Supports
3.2.2Supports
3.3.1Does not supportAn empty required field is marked only by a change of border colour. Nothing identifies the field in error in text.An empty required field is marked only by a change of border colour. Nothing identifies the field in error in text.
3.3.3Supports
3.3.4Supports
2.4.4, 4.1.2Supports
1.1.1, 4.1.2Does not supportThe search button contains only a decorative SVG, so its accessible name is empty.The search button contains only a decorative SVG, so its accessible name is empty.
1.4.5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
2.2.1Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
2.4.1Supports
3.2.3Supports
3.2.4Supports
1.3.1Supports
3.1.1Supports
3.1.2Supports
2.4.2Supports
1.4.1Does not supportColour is the only signal that a field is in error. The submitted contact form in greyscale, where the invalid email field is indistinguishable from the valid fields.Colour is the only signal that a field is in error. The submitted contact form in greyscale, where the invalid email field is indistinguishable from the valid fields.
1.3.3Supports
1.4.3Supports
1.3.2Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.2.1Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.2.2Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.2.5Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.2.4Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
503.4Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
503.4.1Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
503.4.2Not applicableExplanation is not required, Please check detail test resultsExplanation is not required, Please check detail test results
1.4.4Supports
2.4.5Supports
4.1.1Not evaluatedNot yet tested.Not yet tested.

6.EN 301 549

The same results reported against EN 301 549 V3.2.1. Clause 9 is WCAG 2.1 Level A and AA; it is a separate claim and does not change the Section 508 result.

Clause 9: Web

EN 301 549 V3.2.1 · 31 supported, 8 not supported, 11 not applicable, 0 not evaluated, of 50.

ClauseRequirementResultRemarks
9.1.1.1Non-text ContentDoes not supportTrusted Tester 7.A, 7.B, 7.C, 7.DDoes not supportTrusted Tester 7.A, 7.B, 7.C, 7.D
9.1.2.1Audio-only and Video-only (Prerecorded)Not applicableTrusted Tester 16.A, 16.BNot applicableTrusted Tester 16.A, 16.B
9.1.2.2Captions (Prerecorded)Not applicableTrusted Tester 17.ANot applicableTrusted Tester 17.A
9.1.2.3Audio Description or Media Alternative (Prerecorded)Not applicableSettled by 1.2.5 Audio Description.Not applicableSettled by 1.2.5 Audio Description.
9.1.2.4Captions (Live)Not applicableTrusted Tester 17.CNot applicableTrusted Tester 17.C
9.1.2.5Audio Description (Prerecorded)Not applicableTrusted Tester 17.BNot applicableTrusted Tester 17.B
9.1.3.1Info and RelationshipsSupportsTrusted Tester 5.C, 10.B, 10.C, 10.D, 14.A, 14.B, 14.CSupportsTrusted Tester 5.C, 10.B, 10.C, 10.D, 14.A, 14.B, 14.C
9.1.3.2Meaningful SequenceNot applicableTrusted Tester 15.ANot applicableTrusted Tester 15.A
9.1.3.3Sensory CharacteristicsSupportsTrusted Tester 13.BSupportsTrusted Tester 13.B
9.1.3.4OrientationSupportsSupports
9.1.3.5Identify Input PurposeSupportsSupports
9.1.4.1Use of ColorDoes not supportTrusted Tester 13.ADoes not supportTrusted Tester 13.A
9.1.4.2Audio ControlNot applicableTrusted Tester 2.ANot applicableTrusted Tester 2.A
9.1.4.3Contrast (Minimum)SupportsTrusted Tester 13.CSupportsTrusted Tester 13.C
9.1.4.4Resize TextSupportsTrusted Tester 18.ASupportsTrusted Tester 18.A
9.1.4.5Images of TextNot applicableTrusted Tester 7.ENot applicableTrusted Tester 7.E
9.1.4.10ReflowDoes not supportAt 320 CSS pixels wide, the pricing table scrolls in two directions and its last column is cut off.Does not supportAt 320 CSS pixels wide, the pricing table scrolls in two directions and its last column is cut off.
9.1.4.11Non-text ContrastSupportsSupports
9.1.4.12Text SpacingSupportsSupports
9.1.4.13Content on Hover or FocusSupportsSupports
9.2.1.1KeyboardDoes not supportTrusted Tester 4.A, 4.BDoes not supportTrusted Tester 4.A, 4.B
9.2.1.2No Keyboard TrapSupportsTrusted Tester 4.CSupportsTrusted Tester 4.C
9.2.1.4Character Key ShortcutsSupportsSupports
9.2.2.1Timing AdjustableNot applicableTrusted Tester 8.ANot applicableTrusted Tester 8.A
9.2.2.2Pause, Stop, HideNot applicableTrusted Tester 2.B, 2.CNot applicableTrusted Tester 2.B, 2.C
9.2.3.1Three Flashes or Below ThresholdNot applicableTrusted Tester 3.ANot applicableTrusted Tester 3.A
9.2.4.1Bypass BlocksSupportsTrusted Tester 9.ASupportsTrusted Tester 9.A
9.2.4.2Page TitledSupportsTrusted Tester 12.A, 12.BSupportsTrusted Tester 12.A, 12.B
9.2.4.3Focus OrderDoes not supportTrusted Tester 4.FDoes not supportTrusted Tester 4.F
9.2.4.4Link Purpose (In Context)SupportsTrusted Tester 6.ASupportsTrusted Tester 6.A
9.2.4.5Multiple WaysSupportsTrusted Tester 19.ASupportsTrusted Tester 19.A
9.2.4.6Headings and LabelsSupportsTrusted Tester 5.B, 10.ASupportsTrusted Tester 5.B, 10.A
9.2.4.7Focus VisibleSupportsTrusted Tester 4.DSupportsTrusted Tester 4.D
9.2.5.1Pointer GesturesSupportsSupports
9.2.5.2Pointer CancellationSupportsSupports
9.2.5.3Label in NameSupportsSupports
9.2.5.4Motion ActuationSupportsSupports
9.3.1.1Language of PageSupportsTrusted Tester 11.ASupportsTrusted Tester 11.A
9.3.1.2Language of PartsSupportsTrusted Tester 11.BSupportsTrusted Tester 11.B
9.3.2.1On FocusSupportsTrusted Tester 4.ESupportsTrusted Tester 4.E
9.3.2.2On InputSupportsTrusted Tester 5.DSupportsTrusted Tester 5.D
9.3.2.3Consistent NavigationSupportsTrusted Tester 9.BSupportsTrusted Tester 9.B
9.3.2.4Consistent IdentificationSupportsTrusted Tester 9.CSupportsTrusted Tester 9.C
9.3.3.1Error IdentificationDoes not supportTrusted Tester 5.FDoes not supportTrusted Tester 5.F
9.3.3.2Labels or InstructionsSupportsTrusted Tester 5.ASupportsTrusted Tester 5.A
9.3.3.3Error SuggestionSupportsTrusted Tester 5.GSupportsTrusted Tester 5.G
9.3.3.4Error Prevention (Legal, Financial, Data)SupportsTrusted Tester 5.HSupportsTrusted Tester 5.H
9.4.1.1ParsingSupportsMet by HTML content, per the W3C 2023 errata to WCAG 2.0 and 2.1.SupportsMet by HTML content, per the W3C 2023 errata to WCAG 2.0 and 2.1.
9.4.1.2Name, Role, ValueDoes not supportTrusted Tester 2.D, 5.C, 6.A, 7.A, 7.B, 7.C, 7.D, 12.C, 12.DDoes not supportTrusted Tester 2.D, 5.C, 6.A, 7.A, 7.B, 7.C, 7.D, 12.C, 12.D
9.4.1.3Status MessagesDoes not supportAfter the contact form is sent, the confirmation appears on screen but is not announced by a screen reader.Does not supportAfter the contact form is sent, the confirmation appears on screen but is not announced by a screen reader.

7.JIS X 8341-3

The same results as a JIS X 8341-3:2016 test result statement, in Japanese as the standard is.

試験結果

規格の規格番号及び改正年
JIS X 8341-3:2016
目標とする適合レベル及び対応度
レベルAA 一部準拠
試験対象
Example Studio website · https://example.com/
試験実施日
September 10, 2026
試験実施者
Easeweb · Sample Tester
試験対象のウェブページ
  • Home - https://example.com/
  • Services - https://example.com/services
  • Contact - https://example.com/contact

38達成基準中、適合21、不適合6、適用外11、未検証0。

達成基準チェックリスト

番号達成基準適合レベル適用結果備考
1.1.1非テキストコンテンツTrusted Tester 7.A、7.B、7.C、7.DA○×Trusted Tester 7.A、7.B、7.C、7.D
1.2.1音声のみ及び映像のみ(収録済み)Trusted Tester 16.A、16.BA-○Trusted Tester 16.A、16.B
1.2.2キャプション(収録済み)Trusted Tester 17.AA-○Trusted Tester 17.A
1.2.3音声解説、又はメディアに対する代替(収録済み)1.2.5(音声解説)の結果によるA-○1.2.5(音声解説)の結果による
1.2.4キャプション(ライブ)Trusted Tester 17.CAA-○Trusted Tester 17.C
1.2.5音声解説(収録済み)Trusted Tester 17.BAA-○Trusted Tester 17.B
1.3.1情報及び関係性Trusted Tester 5.C、10.B、10.C、10.D、14.A、14.B、14.CA○○Trusted Tester 5.C、10.B、10.C、10.D、14.A、14.B、14.C
1.3.2意味のある順序Trusted Tester 15.AA-○Trusted Tester 15.A
1.3.3感覚的な特徴Trusted Tester 13.BA○○Trusted Tester 13.B
1.4.1色の使用Trusted Tester 13.AA○×Trusted Tester 13.A
1.4.2音声の制御Trusted Tester 2.AA-○Trusted Tester 2.A
1.4.3コントラスト(最低限レベル)Trusted Tester 13.CAA○○Trusted Tester 13.C
1.4.4テキストのサイズ変更Trusted Tester 18.AAA○○Trusted Tester 18.A
1.4.5文字画像Trusted Tester 7.EAA-○Trusted Tester 7.E
2.1.1キーボードTrusted Tester 4.A、4.BA○×Trusted Tester 4.A、4.B
2.1.2キーボードトラップなしTrusted Tester 4.CA○○Trusted Tester 4.C
2.2.1タイミング調整可能Trusted Tester 8.AA-○Trusted Tester 8.A
2.2.2一時停止、停止、非表示Trusted Tester 2.B、2.CA-○Trusted Tester 2.B、2.C
2.3.13回の閃光、又は閾値以下Trusted Tester 3.AA-○Trusted Tester 3.A
2.4.1ブロックスキップTrusted Tester 9.AA○○Trusted Tester 9.A
2.4.2ページタイトルTrusted Tester 12.A、12.BA○○Trusted Tester 12.A、12.B
2.4.3フォーカス順序Trusted Tester 4.FA○×Trusted Tester 4.F
2.4.4リンクの目的(コンテキスト内)Trusted Tester 6.AA○○Trusted Tester 6.A
2.4.5複数の手段Trusted Tester 19.AAA○○Trusted Tester 19.A
2.4.6見出し及びラベルTrusted Tester 5.B、10.AAA○○Trusted Tester 5.B、10.A
2.4.7フォーカスの可視化Trusted Tester 4.DAA○○Trusted Tester 4.D
3.1.1ページの言語Trusted Tester 11.AA○○Trusted Tester 11.A
3.1.2一部分の言語Trusted Tester 11.BAA○○Trusted Tester 11.B
3.2.1フォーカス時Trusted Tester 4.EA○○Trusted Tester 4.E
3.2.2入力時Trusted Tester 5.DA○○Trusted Tester 5.D
3.2.3一貫したナビゲーションTrusted Tester 9.BAA○○Trusted Tester 9.B
3.2.4一貫した識別性Trusted Tester 9.CAA○○Trusted Tester 9.C
3.3.1エラーの特定Trusted Tester 5.FA○×Trusted Tester 5.F
3.3.2ラベル又は説明Trusted Tester 5.AA○○Trusted Tester 5.A
3.3.3エラー修正の提案Trusted Tester 5.GAA○○Trusted Tester 5.G
3.3.4エラー回避(法的、金融及びデータ)Trusted Tester 5.HAA○○Trusted Tester 5.H
4.1.1構文解析W3Cの2023年の正誤表により、HTMLのコンテンツは適合とみなされるA○○W3Cの2023年の正誤表により、HTMLのコンテンツは適合とみなされる
4.1.2名前(name)・役割(role)及び値(value)Trusted Tester 2.D、5.C、6.A、7.A、7.B、7.C、7.D、12.C、12.DA○×Trusted Tester 2.D、5.C、6.A、7.A、7.B、7.C、7.D、12.C、12.D

Want a report like this for your site?

Tell me which pages and flows matter most. I will confirm the scope and price before any testing starts.