Sample record. This is a shortened example of the Accessibility Evidence File Accessrank prepares for each client. It is based on a real engagement with every identifying detail removed: the store name, website, people, products and contact details are invented, and dates are left out. A real record dates every entry. Remediation can take anywhere from a few days to a few months, depending on the site.
Accessibility Evidence File
Example Store · store.example · Client packet · Version 1.0
Accessrank, Inc. · Access & Discovery Solutions · accessrank.ai
Contents
| Section | What it answers |
|---|---|
| Cover memo | What this record is, key dates, and how to use it |
| Section 1 — Baseline audit | What the store knew, and when |
| Section 2 — Remediation log | What has been fixed, and when |
| Section 3 — Conformance summary | Where the store stands now, and what was tested |
| Section 4 — Public accessibility statement | Whether the program is public, and the inquiry log |
| Section 5 — Ongoing monitoring record | Whether the program is continuous: every scan, dated |
| Section 6 — Manual and assistive-technology testing | Whether a person has verified the work |
| Section 7 — Program engagement and scope | What the store has committed to, and known limits |
| Language guidelines and disclaimer | What to say, what not to say, and the limits of this record |
| Exhibits and attestation forms | Supporting documents and signable forms |
Status at a glance
| Protection level | Deter: every finding an automated scan can see is fixed and monitored. Verify: human testing in progress (Section 6) |
|---|---|
| Lighthouse accessibility | 88 at baseline; 93 after the first round of fixes; 100 after the second, and 100 again at the latest re-test |
| Automated violations | 0 WCAG 2.2 A/AA violations on an 11-page re-test of the live site |
| Remediation log | 42 fixes and 3 approved changes. 40 fixes closed and passed on re-test; 2 closed in code and waiting for confirmation by a person (Section 6) |
| Accessibility statement | Approved by the store owner and published, linked from every page footer (Section 4) |
| Still open | Screen reader and phone testing (Section 6); audio description for one brand video, awaiting the owner’s decision |
Cover memo
↑ ContentsThis record documents the website accessibility program for store.example, which began with a baseline audit before any fixes. It is maintained by Accessrank, Inc. and refreshed after each scan and on request. Every item is dated, and every finding is measured against WCAG 2.2 Level A and AA.
It is organized so a reader, such as the store’s attorney or insurer, can answer three questions quickly: what the store knew and when, what has been fixed and when, and what the store is doing on an ongoing basis. Section 1 establishes the starting point. Sections 2 and 3 show the fixes and where the store stands now. Sections 4 through 7 show whether the program is public, continuous, checked by a person, and committed.
| Stage | By |
|---|---|
| Baseline audit, before any fixes | Store + Accessrank |
| Remediation, in rounds, each published and re-tested | Accessrank, Inc. |
| Owner approvals of every visible change | Store owner |
| Accessibility statement approved and published | Store owner; Accessrank |
| Automated re-test after each publish | Accessrank, Inc. |
| Manual and assistive-technology testing | Accessrank + testers (in progress) |
| Monitoring and certificates | Accessrank, Inc., quarterly and on request |
Section 1
Baseline audit
↑ ContentsThe baseline records the state of store.example before any fixes. It shows, with date stamps, that the store identified its own accessibility issues and acted on them.
| Item | Baseline |
|---|---|
| Audit | Google Lighthouse accessibility report of the home page, and a review of product and collection pages by Accessrank (12 products, 2 collections) |
| Tooling | Google Lighthouse; Accessrank automated scan of the live site in a real browser against WCAG 2.2 A/AA |
| Scope | Customer-facing pages and templates. Checkout and customer account pages are hosted by the store platform and are out of scope |
| Lighthouse accessibility score | 88 / 100 |
| Findings | 4 failed Lighthouse checks on the home page (a pop-up with no name, focusable items inside hidden areas, low-contrast text, small touch targets), plus missing image descriptions found in the page review |
| Attestation | Signed by Accessrank: Form A1, attached |
Section 2
Remediation log
↑ ContentsEvery fix below was made in the store’s theme code or content, not through an overlay or widget. Theme changes were tested first on a copy of the theme and then published. In a real record every entry carries the date it went live; dates are left out of this sample. Entries are never edited after the fact; a correction is a new row. The full log is shown: 42 fixes and 3 approved changes, newest first.
| Finding | WCAG | Pages | How fixed | Status |
|---|---|---|---|---|
| Accessibility statement (approved by the store owner) | — | Site-wide | Published as approved and linked from every page footer | Closed Live |
| Accessrank footer credit (approved by the store owner) | — | Site-wide footer | Added as shown in the approval packet | Closed Live |
| Who handles accessibility reports (approved by the store owner) | — | Accessibility statement | Accessrank receives reports and replies for the store, with a copy to the owner, within 2 business days | Closed Live |
| A sold-out product button was announced to screen readers as disabled, but pressing Space on it still fired a click. A control that says it is disabled but still activates is a name, role and value fault. Traced by instrumenting the browser’s click function on the live page: the call came from an inline script in the theme layout, not from the theme’s asset files, which is why a search of those files had not found it | 4.1.2 | Shop | A guard in the theme’s accessibility script stops the Space key on the two sold-out controls only, and only while they are marked disabled. For the visitor the key does nothing and the page does not scroll; what changes is that no click is fired Re-test: Published on its own, on a copy of the live theme. Before publishing, every layout, section, snippet and template file was compared with the live theme by checksum: only the two intended files differed. On the live site, Space on a sold-out control produced no click and focus stayed put; on an available product Space still adds to the cart | Closed Passed re-test |
| Each product tile’s “View” link opens a product panel in place (the page goes from 339 to 533 visible elements), but the link carried no expanded state and no reference to the panel, so a screen reader user was not told that anything had opened, or where | 4.1.2 | Shop | Each link now names the panel it controls and reports whether it is open, read from what the panel is actually showing rather than from the address bar. The links keep working as links if scripts do not run Re-test: All 12 product links checked on the live site: collapsed on load, and opening two products leaves exactly those two reported as open. Published on its own; all 377 theme files compared before publishing, one changed | Closed Passed re-test |
| All 28 quantity buttons on the shop grid were named only “Increase quantity” or “Decrease quantity.” Read as a list of controls, nothing told twelve products’ buttons apart | 2.4.6 best practice | Shop | Each button is now named for its product; the four inside the product panel take the name of the product that is open Re-test: All 24 tile buttons named for their product on the live site; the panel buttons fall back to a generic label when no product is showing | Closed Passed re-test |
| Correction to the captions entry below. The first caption file was timed from silence detection over the film’s music bed rather than from measured speech, so its cues did not match the audio. Captions that are not synchronised do not satisfy 1.2.2, so that entry overstated the position until this correction | 1.2.2 | About | Rebuilt from measurement. A speech detector separated speech from music (18 segments, 173 seconds of speech); speech recognition then gave word-level timings for 468 words, aligned to the approved caption text (81% matched directly, the rest interpolated across short gaps). Cues were re-cut at sentence boundaries so no caption appears before it is spoken; the old file ran up to five seconds early Re-test: On the live site: 43 cues, all parsed by the browser, captions showing. Checked against three timings the store owner read from the player clock (0:09, 1:03 and 3:02) against 9.30, 62.74 and 182.28 seconds in the new file. Two lines at most, none faster than 21 characters per second, and every word of the approved text kept | Closed Passed re-test |
| The new text alternative for the video set white text on the About page’s light-blue gradient: 3.44:1 for dialogue, 3.23:1 for the summary, and 2.90:1 and 2.83:1 for the descriptions. The fix for one criterion had introduced a failure of another | 1.4.3 | About | Covered by the flat page background described in the heading entry below Re-test: Re-measured on the live page: summary and dialogue 9.46:1; notes and descriptions 7.35:1, against 4.5:1 required | Closed Passed re-test |
| The text alternative’s scrolling box (1,466 px of scroll) contained nothing focusable, so a keyboard user could not reach it or scroll it, and everything below its fold was out of reach without a mouse | 2.1.1 | About | The box is now a named, focusable region with a visible focus outline Re-test: On the live page it takes focus and scrolls by keyboard | Closed Passed re-test |
| The heading above the video, white 40 px bold type, sat directly on the page’s light-blue gradient: 2.36:1, under the 3:1 allowed even for large text. Pre-existing, not caused by the video work | 1.4.3 | About | The gradient was replaced by one flat blue, the dark color the gradient already ended on, so it is the same brand color. No panel or bar behind any text. Limited to the About page Re-test: White text now 9.46:1. A sweep of every visible text element on that background found no failures. Automated scan: 0 violations, 34 passes. The 30 items the scanner could not decide (text over the footer’s gradient) were measured by hand against the gradient’s own colors: all 8 text styles pass | Closed Passed re-test |
| The brand video had captions but no text alternative, so a visitor who cannot see it had no account of what it shows | 1.2.3 | About | A full text alternative under the player, opened and closed by keyboard: 21 descriptions of what is on screen interleaved with 19 passages of dialogue, covering all 35 shots, written after scene detection and a frame-by-frame review Re-test: Live; closed by default, with a 46 px control. Speakers are not labeled line by line, and the record says why: who is on screen was verified from the footage, who is speaking was not | Closed Passed re-test |
| The 3-minute brand video was embedded from a channel the store does not manage, so its only captions were the automatic ones: no punctuation, no speaker or sound cues, no checked accuracy, and turned off by default | 1.2.2, 1.2.3 (partial) | About | The video is now served from the store’s own files as a native video with a caption track, shown by default. Re-encoded at 1920×1080, and the player corrected to a true 16:9 ratio, which also removed the black bars Re-test: Live: 42 caption cues parsed and showing by default; automated scan 0 violations. Caption text came from speech recognition and was corrected by hand against the audio. Audio description (1.2.5) remains open and is listed as an open item | Closed Passed re-test |
| Following an in-page link put the target under the sticky header, with all 161 px of it covered, including the main content the skip link jumps to | 2.4.11 | Site-wide | Scroll spacing tied to the theme’s own header height, so targets stop below the header at every screen width Re-test: Target now lands at 161 px, level with the header’s bottom edge: 0 px covered, where it had been 161 px. Automated scan 0 violations | Closed Passed re-test |
| The header account link was 0 px wide: invisible and impossible to click, but still reached by the Tab key and read aloud. It was the only route to the account area anywhere on the site | 2.5.8, 4.1.2 | Site-wide header | The link was moved, not copied, into the top strip beside the cart and given a real size, so only one account link exists Re-test: 73 × 28 px on desktop and 44 × 28 px on phones, against a 24 × 24 minimum; named “Log in,” and “Account” when signed in; 6.73:1 contrast; visible focus outline; 0 violations | Closed Passed re-test |
| On phones, the shipping notice in the top strip ran underneath the cart and account icons, and the strip did not line up with the header below it | 1.4.10, 1.4.4 supporting | Site-wide header | The strip now lines up with the header column, and the notice reserves room measured from the icons, switching to a shorter sentence only when the full one will not fit Re-test: One line at every width from 2,155 px down to 320 px, and never reaching the icons | Closed Passed re-test |
| The related-products row on product pages was held at near-zero opacity until scrolled into view, so its heading, 12 product names and prices measured 1.01:1, near-white on white | 1.4.3 | Product pages | Hidden state corrected to fully hidden, respecting the visitor’s reduced-motion setting, with a fallback that shows the row if scripts never run Re-test: 0 violations on the live product page measured from the top, where the previous theme returned 26; the fade-in still runs | Closed Passed re-test |
| A large headline over a bright part of a photo was hard to read | 1.4.3 | Shop | Dark backing behind the headline only; photo and products not darkened Re-test: Lowest point 4.1:1 (large text needs 3:1) | Closed Passed re-test |
| A heading and first paragraph over a photo were hard to read | 1.4.3 | Content page | Dark backing behind the heading and paragraph Re-test: Heading 8.8:1 and paragraph 7.9:1 at worst | Closed Passed re-test |
| An embedded video had no name | 4.1.2 | About | Descriptive title added to the video frame Re-test: Title present on the live page; 0 violations | Closed Passed re-test |
| The store locator’s main title was plain text, not a heading | 1.3.1 | Store locator | Marked as a level-2 heading Re-test: Appears in the page’s heading outline | Closed Passed re-test |
| A section heading skipped a level | 1.3.1 best practice | Shop | Set to level 2 Re-test: No skipped level in the outline | Closed Passed re-test |
| A large title repeated the page’s main heading as a second heading | — best practice | Content page | Taken out of the heading outline; still visible Re-test: Outline shows the main heading only | Closed Passed re-test |
| The header menu did not tell assistive technology which page you are on | 1.3.1 | Site-wide | Current-page marker added to the active menu link Re-test: Checked on three pages | Closed Passed re-test |
| Four social links in the header open a new tab without saying so | 3.2.5 AAA, best practice | Site-wide | “(opens in a new tab)” added to each link’s name Re-test: All four names read correctly | Closed Passed re-test |
| Hero slideshow images had no useful descriptions | 1.1.1 | Home | Description for each slide, editable by the store in its theme editor Re-test: 0 violations on the live site | Closed Passed re-test |
| A banner image and a recipe image had no descriptions | 1.1.1 | Home | Descriptions set in the store’s file library, so they apply in every theme Re-test: 0 violations on the live site | Closed Passed re-test |
| The skip-to-content link did not lead anywhere useful | 2.4.1 | Site-wide | Pointed at the main content Re-test: Reaches the main content | Closed Passed re-test |
| Two product names were read aloud with no space between the words | 1.3.1 | Home, Shop | Spacing restored in the markup Re-test: Checked in the browser’s accessibility tree | Closed Passed re-test |
| An invalid email in the newsletter form showed an error that screen readers did not announce | 3.3.1, 4.1.3 | Site-wide footer | Error now shown in a status line that is announced Re-test: Invalid email tested; a valid email was not submitted | Closed Passed re-test |
| A tagline was marked up as a heading | 1.3.1 | Home | Heading markup removed Re-test: 0 violations | Closed Passed re-test |
| Review badge text measured 4.23:1 | 1.4.3 | Product | Darkened to 5.3:1 Re-test: 0 violations | Closed Passed re-test |
| The main page heading was hidden from everyone on four pages | 1.3.1, 2.4.6 | Four content pages | Heading made available to assistive technology Re-test: Heading present on all four | Closed Passed re-test |
| The brand heading ran two words together | 1.3.1 | Home | Space restored Re-test: 0 violations | Closed Passed re-test |
| A wholesale note measured 4.48:1 at 14 px, just under the 4.5:1 minimum | 1.4.3 | Store locator | Same warm gray one shade darker: 4.72:1 Re-test: An 11-page scan with the full rule set, best-practice rules included: 0 violations on every page | Closed Passed re-test |
| The product review widget brings its own colors, and two fell short: review dates and rating counts at 4.23:1, and “Verified” links at 3.39:1 | 1.4.3 | Product pages | Both darkened within the same hue: 5.3:1 and 5.1:1 Re-test: 0 violations on the 11-page scan. The widget belongs to a third party, so it is re-checked after each of its updates | Closed Passed re-test |
| White text on the brand yellow in the About page slider measured 1.68:1. The site’s own navy would only have reached 4.01:1 and still failed | 1.4.3 | About | Text changed to a deeper navy from the same family: 6.68:1. Limited to the slider, so no other yellow panel changed (approved by the owner) Re-test: 0 violations on the 11-page scan | Closed Passed re-test |
| The cart icon’s click area measured 45 × 23 px, one pixel under the 24 px minimum | 2.5.8 | Site-wide header | Four pixels of padding above and below; the icon did not move Re-test: 0 violations on the 11-page scan, target-size rule included | Closed Passed re-test |
| Slideshow previous and next buttons were 20 × 20 px and 10 px apart | 2.5.8 | Site-wide | Each enlarged to 32 × 32 px around the same center, so the arrows did not move Re-test: 0 violations on the 11-page scan, target-size rule included | Closed Passed re-test |
| The pause button added for moving content landed on top of a carousel’s Next arrow, so neither could be hit reliably | 2.5.8 | Store locator | Pause button moved just outside the strip, level with the arrows and 24 px clear Re-test: 0 violations on the 11-page scan, target-size rule included | Closed Passed re-test |
| The “Skip to content” link stayed invisible while focused. The theme’s own stylesheet hid it with rules the platform’s reveal could not override, so a sighted keyboard user tabbed onto something they could not see | 2.4.1, 2.4.7 | Site-wide | Shown on focus as a navy button at top left, white text at 11.3:1, with a yellow focus ring Re-test: The rule is live, but whether the link is visible while focused can only be confirmed by a person using a keyboard. Queued for the manual pass in Section 6 | Closed in code Manual check pending |
| Four pages hid their main section entirely, which also removed each page’s main heading from the accessibility tree | 1.3.1, 2.4.6 | Four content pages | The section stays in the accessibility tree and is hidden from view instead, so the heading is announced and nothing changes on screen Re-test: 0 violations on the 11-page scan; no missing page heading on any of the four | Closed Passed re-test |
| The newsletter pop-up and the cart drawer were announced as dialogs but did not behave as dialogs: focus never moved inside them, so Escape never worked | 2.1.2, 2.4.3, 4.1.2 | Site-wide | Each dialog now moves focus inside when it opens, keeps Tab inside, closes with Escape or a click outside, and returns focus to the button that opened it, whichever code opened it Re-test: Live, but focus trapping and focus return cannot be confirmed by an automated scan. Queued for the manual pass in Section 6 | Closed in code Manual check pending |
| Markup repeated across many sections had naming faults no single edit would reach: pasted-in icon files repeated the same ids, icons inside labeled buttons were read twice, pop-ups had no name (the platform’s own privacy banner among them), and embedded frames had no title | 1.1.1, 4.1.1, 4.1.2 | Site-wide | A pass that runs on every page, including content loaded later such as product panels and the cart, removes duplicate ids, hides decorative icons, names dialogs and titles frames. A later revision cut about 2.5 seconds of processing on a phone Re-test: 0 violations on the 11-page scan. The code is dated; the exact publish day was not recorded, so this date is the earliest publish the record can show, and is stated as such | Closed Passed re-test |
| Controls that responded to a mouse click could not be reached or used by keyboard: quick-add and add-to-cart controls, the product details accordion, and carousel tiles | 2.1.1, 4.1.2 | Site-wide | Each now behaves as a button: reachable with Tab and working with Space. Accordion headings report whether they are open Re-test: 0 violations on the 11-page scan. Space tested directly on the live add-to-cart control, with the click suppressed so nothing entered the cart. Same earliest-publish dating as above | Closed Passed re-test |
| “Free shipping – Quick add” button text was below the contrast minimum | 1.4.3 | Product tiles | Button color darkened only as much as needed Re-test: Live and passing on later scans | Closed Passed re-test |
Section 3
Conformance summary
↑ ContentsWhen human testing is part of the engagement, a full criterion-by-criterion Accessibility Conformance Report on the VPAT® form is issued after that testing (Section 6), because many WCAG criteria can only be confirmed by a person. This interim summary shows the automated status. It is a report of findings, not a certification.
| Measure | Result |
|---|---|
| WCAG 2.2 criteria in scope | 55 (31 Level A, 24 Level AA) |
| Criteria with findings at baseline | 1.1.1 Non-text content; 1.4.3 Contrast; 2.5.8 Target size; 4.1.2 Name, role, value |
| Automated violations at latest re-test | 0 on 11 pages of the live site: home, shop and about pages, two product pages, cart, search, privacy policy, the 404 page and two content pages |
| Checked by hand on desktop | Keyboard order and visible focus on the home page; cart drawer and cookie dialog by keyboard; text over photographs; slideshow controls; linked documents (none found) |
| Not yet tested | Real screen readers (VoiceOver, NVDA, JAWS); phones, including the mobile menu; reflow at 320 px and zoom to 200% |
Section 4
Public accessibility statement
↑ ContentsThe statement was approved by the store owner and then published, linked from the footer of every page. It claims no conformance. It names WCAG 2.2 Level AA as the target, describes what has actually been done, and lists known limits, including that testing with screen readers is still under way. It will be updated with the results of that testing.
| Item | Value |
|---|---|
| Accessibility contact | Accessrank receives reports and replies for the store, with a copy to the store owner |
| Reply time published | 2 business days |
Accessibility inquiry log
| Date received | Channel | Issue raised | Response | Resolved |
|---|---|---|---|---|
| — | — | No inquiries recorded yet | — | — |
Section 5
Ongoing monitoring record
↑ ContentsEach scan is recorded with its date and result. Scores from different tools are listed separately and are never added together. A signed monitoring certificate (Form A2) is issued after each scan.
| Measure | Before fixes | After fixes |
|---|---|---|
| Lighthouse accessibility | 88 | 100 |
| Accessrank score (accessibility) | Not run before fixes | 98, no WCAG failures found |
| Automated violations | 4 failed checks, home page | 0 on 11 pages |
| On-page SEO (reported separately) | — | 100, 14 of 14 checks |
| AI agent readiness (reported separately) | — | 100, 8 of 8 checks |
Scan log
| Stage | Tool | Result |
|---|---|---|
| Baseline | Google Lighthouse | Accessibility 88; 4 failed checks on the home page |
| After the first round | Google Lighthouse | Accessibility 93 |
| After the second round | Google Lighthouse | Accessibility 100, confirmed on desktop and mobile |
| After the second round | Accessrank re-test of 57 pages | 62 speed and stability issues confirmed fixed; contrast and naming items still open and carried into the next round |
| After the third round | Automated scan (axe-core) | 0 violations on the pages scanned |
| After the fourth round | Accessrank free check | Accessrank score 98; 0 of 55 criteria failing; on-page SEO 100; AI agent readiness 100 |
| After the fourth round | Automated scan (axe-core), full rule set | 1 contrast finding on product pages, fixed and published the same day; then 0 violations on 11 pages |
| After the fourth round | Google Lighthouse | Accessibility 100, performance 92, best practices 100, SEO 100 |
Section 6
Manual and assistive-technology testing
↑ ContentsIn progress. Automated scans cannot confirm every WCAG criterion. A person using a keyboard and a screen reader checks what a scan cannot, such as whether a page makes sense read aloud and whether a purchase can be completed without a mouse. A 14-step test script covers the core shopping path: finding a product, reading its details, choosing options, adding to the cart and using the cart. When testing is done, this record is updated with the results, the tester’s signed attestation and any new findings, and the accessibility statement is updated to match.
Section 7
Program engagement and scope
↑ Contents| Item | Detail |
|---|---|
| Target standard | WCAG 2.2 Level A and AA |
| Scope | store.example, customer-facing pages and templates. Platform-hosted checkout and account pages excluded |
| Method | Fixes in the theme code and store content; no overlay or widget |
| Monitoring | Continuous automated monitoring, with a dated certificate after each scan |
| Store responsibilities | Keep the accessibility contact monitored; tell Accessrank before theme, app or platform changes; add descriptions to new images |
Limits outside the theme
| Area | Owner | Action |
|---|---|---|
| Checkout and payment pages | Store platform | Documented as a known limitation |
| Subscription widget | App vendor | Issues reported to the vendor |
| Product review widget | App vendor | Colors corrected on the store’s side; re-checked after vendor updates |
Language guidelines and disclaimer
↑ Contents| Say | Do not say |
|---|---|
| Working toward full WCAG 2.2 AA conformance | Fully accessible |
| Audited and monitored by Accessrank | Certified accessible, or lawsuit-proof |
| Fixes are made in the site’s code | Protected by an accessibility widget |
| Conforms to WCAG 2.2 Level AA on [date], per the attached report (only after manual testing is complete and attested) | ADA compliant |
Disclaimer. This record reports findings against WCAG 2.2 Level A and AA as of the dates stated. It is not legal advice, does not certify compliance with the Americans with Disabilities Act or any other law, and does not guarantee any outcome in any claim or proceeding.
Exhibits and attestation forms
↑ Contents| Exhibit | Document |
|---|---|
| A | Baseline audit reports |
| B | Remediation log as a spreadsheet, and the owner’s approvals of visible changes |
| C | Accessibility Conformance Report (VPAT®), issued when human testing is part of the engagement |
| D | Accessibility statement as published, with a dated screenshot |
| E | Monitoring certificates, in date order |
| F | Manual and assistive-technology testing attestations |
Form A2: Monitoring certificate
| Site | store.example |
| Scan date | [Date of scan] |
| Tool | axe-core, WCAG 2.0–2.2 A/AA plus best practice, live site |
| Pages scanned | 11 |
| Result | 0 violations |
I certify that the scan identified above was run on the date stated and that the figures above are the results the tool reported. This certificate reports a scan result. It does not certify conformance with WCAG or compliance with any law.
| Signature | |
| Printed name | |
| Date signed |