Semantic and Keyboard Access
Landmarks, headings, links, forms, details, focus order, skip navigation, labels, and errors use native behavior.
Access Is Part of Quality
Technology Information Should Work for More People.
The MITEC website targets WCAG 2.2 Level AA and is designed for keyboard, mouse, touch, screen-reader semantics, zoom and reflow, reduced motion, forced colors, and modern desktop and mobile browsers. Accessibility is tested throughout implementation rather than added after design.
Contact Mitec About AccessibilityResponsive Visual Access
Color contrast, 320-pixel layouts, 400% reflow, touch targets, reduced motion, and forced colors receive explicit checks.
Assistive Technology Support
Semantic HTML, keyboard operation, screen-reader support, visible focus, and responsive layouts are maintained together.
Accessibility Commitments
Mitec aims for WCAG 2.2 Level AA across navigation, forms, content, contrast, keyboard access, zoom, reduced motion, and mobile layouts.
Accessibility needs vary by person, device, browser, and assistive technology. Contact Mitec when a barrier prevents you from completing a task.
- WCAG 2.2 AA engineering target
- Keyboard and visible focus support
- Responsive zoom and reflow
- Screen-reader-friendly structure
Ask for Help or Report a Barrier
If content, navigation, contrast, language, focus, a form, a document, or another feature creates a barrier, contact Mitec with the page address, browser, device, assistive technology when relevant, and the task you were trying to complete.
Do not include passwords or sensitive records. Mitec can offer the published phone and email as alternate contact paths while the issue is reviewed.
- Page address and task
- Browser and device
- Assistive technology when relevant
- Phone and email alternatives
Clear Process
How Accessibility Issues Are Handled
-
Receive
Record the affected page, task, environment, observed barrier, and safe reply method.
-
Reproduce
Test the relevant browser, input method, viewport, language, and semantic behavior.
-
Correct
Fix the canonical component or content source, add a regression test, and rebuild.
-
Verify
Rerun automated and manual evidence and communicate the result or remaining boundary.
Useful Answers
Accessibility Questions
Does a Lighthouse Score of 100 Prove Full WCAG Conformance?
No. Lighthouse and axe cover detectable issues, while WCAG also requires manual and contextual evaluation. The project combines tools and manual evidence and does not present one score as legal certification.
Which Browsers and Screen Sizes Are Tested?
Automated tests check the site in the Chromium, Firefox, and WebKit browser engines at widths from 320 to 1920 CSS pixels, and pages are also reviewed visually in desktop Chrome. Testing in Safari on Apple devices and with screen readers and other assistive technologies is not complete yet. Automated testing does not replace testing with people who use assistive technology.
How Can I Request an Alternate Way to Contact Mitec?
Use (805) 643-4375 or support@mitec.net. Explain the task and preferred communication format without sending sensitive credentials or records.
Next Step
Report a Barrier or Request Another Contact Path.
Include the page, task, browser, device, and assistive technology when relevant.
Contact Mitec About Accessibility →