Accessibility Statement for ledmyplace.com
-
WCAG 2.2 Level AA
-
EN 301 549 v3.2.1 (European standard)
-
Section 508 of the Rehabilitation Act (United States)
-
Title II and III of the Americans with Disabilities Act (ADA)
- Weekly automated scans identify all critical, machine-detectable issues across pages using WCAG logic
- A defined set of 22 manual checks is conducted internally by our team based on guided instructions from the platform
- Ongoing issue tracking automatically detects regressions and recognizes resolved items between scans
| WCAG Criterion | Issue Description | Source |
|---|---|---|
| Best Practice | Ensure every id attribute value in the document is unique | Automated |
| 4.1.2: Name, Role, Value | Verify that iframe and frame elements have an accessible name via the title attribute | Automated |
| Best Practice | Check that heading levels follow a logical hierarchical sequence without skipping levels | Automated |
| Best Practice | Ensure visible labels match the element accessible name for voice control users | Automated |
| Best Practice | Check that landmark regions have unique accessible names to help users distinguish between them | Automated |
| 1.4.3: Contrast (Minimum) | Evaluate text and background color combinations meet the 4.5:1 AA contrast ratio | Automated |
| 4.1.2: Name, Role, Value | Verify that select dropdown elements have an accessible name through labels or ARIA attributes | Automated |
| Best Practice | Check that the page includes at least one level-one heading to establish content hierarchy | Automated |
| Best Practice | Detect heading elements that contain no visible or programmatic text content | Automated |
| 4.1.2: Name, Role, Value | Verify all button elements have accessible text content for assistive technologies | Automated |
| Best Practice | Ensure id attributes on active focusable elements are unique | Automated |
| 4.1.2: Name, Role, Value | Verify that every form control has an associated visible label that is programmatically linked | Automated |
| 2.4.4: Link Purpose (In Context) | Confirm that all hyperlink elements have meaningful, discernible text content | Automated |
| Best Practice | Identify images whose alternative text duplicates adjacent visible text content | Automated |
| Best Practice | Check all visible page content is within defined landmark regions for navigation | Automated |
| 4.1.2: Name, Role, Value | Identify the ARIA attributes that conflict with an element\'s assigned role per the specification | Automated |
| 4.1.2: Name, Role, Value | Confirm all ARIA attribute values conform to the allowed value types defined in the specification | Automated |
| 3.1.3 Unusual Words (AAA), 3.1.4 Abbreviations (AAA), 3.1.5 Reading Level (AAA), 3.1.6 Pronunciation (AAA) | Content Clarity and Linguistic Support | Manual |
| 1.3.4 Orientation (AA) | Content Orientation Flexibility | Manual |
| 2.4.4 Link Purpose (In Context) (A), 2.4.9 Link Purpose (Link Only) (AAA), "4.1.2 Name, Role, Value (A)", 2.4.6 Headings and Labels (AA), 2.5.3 Label in Name (A) | Descriptive Context for Interactive Elements | Manual |
| 2.1.1 Keyboard (A), 1.3.1 Info and Relationships (A), 3.3.1 Error Identification (A), "4.1.2 Name, Role, Value (A)", 2.4.6 Headings and Labels (AA), 1.3.5 Identify Input Purpose (AA), 3.2.4 Consistent Identification (AA), 3.2.2 On Input (A), 3.2.6 Consistent Help (A), 3.3.2 Labels or Instructions (A), 1.4.1 Use of Color (A), 3.3.3 Error Suggestion (AA), 3.3.7 Redundant Entry (A), 3.3.8 Accessible Authentication (Minimum) (AA), "3.3.4 Error Prevention (Legal, Financial, Data) (AA)", 3.3.9 Accessible Authentication (Enhanced) (AAA), 3.3.6 Error Prevention (All) (AAA) | Form Submission & Error Handling for Assistive Technologies | Manual |
| 1.4.13 Content on Hover or Focus (AA), 2.1.1 Keyboard (A), 1.3.1 Info and Relationships (A) | Hidden and Revealed Content Accessibility | Manual |
| 1.3.6 Identify Purpose (AAA) | Identify Purpose of Components and Regions | Manual |
| 1.1.1 Non-text Content (A), 1.4.5 Images of Text (AA), 1.3.3 Sensory Characteristics (A) | Image Text Alternatives and Avoiding Images of Text | Manual |
| 2.5.4 Motion Actuation (A), 2.5.7 Dragging Movements (AA), 2.5.1 Pointer Gestures (A), 2.5.2 Pointer Cancellation (A) | Input Interaction Accessibility | Manual |
| 2.5.5 Target Size (AAA) | Interactive Element Sizing | Manual |
| 2.1.1 Keyboard (A), 2.4.7 Focus Visible (AA), 2.4.11 Focus Not Obscured (Minimum) (AA), 2.1.2 No Keyboard Trap (A), 2.4.3 Focus Order (A), 1.4.11 Non-text Contrast (AA), 2.4.13 Focus Appearance (AAA), 2.4.12 Focus Not Obscured (Enhanced) (AAA) | Keyboard Focus Management, Order, and Visibility | Manual |
| 2.1.1 Keyboard (A), 2.4.7 Focus Visible (AA), 1.4.13 Content on Hover or Focus (AA), 3.2.3 Consistent Navigation (AA), 2.4.1 Bypass Blocks (A), 2.1.3 Keyboard (No Exception) (AAA) | Keyboard Navigation and Full Access | Manual |
| "4.1.2 Name, Role, Value (A)", 1.4.13 Content on Hover or Focus (AA), 4.1.3 Status Messages (AA) | Live Content Updates and Screen Reader Announcements | Manual |
| 1.2.1 Audio-only and Video-only (Prerecorded) (A), 1.2.2 Captions (Prerecorded) (A), 1.2.4 Captions (Live) (AA), 1.2.3 Audio Description or Media Alternative (Prerecorded) (A), 1.2.5 Audio Description (Prerecorded) (AA), 1.4.2 Audio Control (A), "2.2.2 Pause, Stop, Hide (A)", 1.2.7 Extended Audio Description (Prerecorded) (AAA), 1.2.8 Media Alternative (Prerecorded) (AAA), 1.2.9 Audio-only (Live) (AAA), 1.4.7 Low or No Background Audio (AAA) | Media Captions, Transcription, and Control of Automatically Playing Media | Manual |
| 2.1.1 Keyboard (A), "4.1.2 Name, Role, Value (A)", 1.3.1 Info and Relationships (A), 2.4.11 Focus Not Obscured (Minimum) (AA) | Modal Dialogs (Focus Trapping & Role Compliance) | Manual |
| 2.3.1 Three Flashes or Below Threshold (A), 2.3.2 Three Flashes (AAA), 2.3.3 Animation from Interactions (AAA) | Motion, Animation, and Flashing Content | Manual |
| 2.1.1 Keyboard (A), "4.1.2 Name, Role, Value (A)", 1.3.1 Info and Relationships (A), 2.4.11 Focus Not Obscured (Minimum) (AA), 3.2.1 On Focus (A) | Navigation Menu Focus Management & Interactive Element Clarity | Manual |
| 3.1.1 Language of Page (A), 3.1.2 Language of Parts (AA) | Page Language and Language of Parts | Manual |
| 1.3.1 Info and Relationships (A), 1.3.2 Meaningful Sequence (A), "4.1.2 Name, Role, Value (A)", 2.1.4 Character Key Shortcuts (A) | Semantic Structure and Data Integrity of Tables | Manual |
| 1.4.4 Resize text (AA), 1.4.10 Reflow (AA), 1.4.12 Text Spacing (AA), 2.5.8 Target Size (Minimum) (AA), 1.4.8 Visual Presentation (AAA) | Text Legibility & Layout Integrity at High Zoom Levels | Manual |
| 2.2.1 Timing Adjustable (A) | Time Limit Controls | Manual |
| 3.2.5 Change on Request (AAA), 3.3.5 Help (AAA), 2.2.4 Interruptions (AAA), 2.2.6 Timeouts (AAA) | User Control, Interruptions, and Data Preservation | Manual |
| 2.4.8 Location (AAA) | User Location and Orientation | Manual |
| WCAG Criterion | Issue Description | Pages Affected |
|---|---|---|
| Best Practice | Verify that iframe and frame elements have an accessible name via the title attribute | 3 |
-
Automated Testing:
Conducted weekly using the AccessibilityChecker.org testing platform, covering both mobile and desktop interfaces to identify machine-detectable issues. -
Manual Testing:
A set of 17 essential manual tests is performed to assess aspects that require human judgment, using popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices. -
Interactive Element Testing (User-Performed):
Interactive components (such as forms, menus, dialogs, and dynamic content) are evaluated through user testing using the AccessibilityChecker browser extension. -
Assistive Technology Compatibility:
Tested with major screen readers (e.g., NVDA, JAWS, VoiceOver) and across popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices.
AccessibilityChecker.org provides automated testing results and supports manual and interactive testing; however, completion of all manual and interactive tests remains the sole responsibility of the customer. The customer is also fully responsible for implementing any recommended corrections or remediation actions.
This tool is not all inclusive, and does not constitute legal advice, a legal guarantee, or certification of compliance with any accessibility laws, regulations, or standards. Accessibility requirements may change over time, and compliance depends on ongoing maintenance and review. The customer is solely responsible for ensuring the contemplated domain is reviewed periodically and remains compliant with applicable accessibility requirements.