Keyboard access
Primary navigation, dialogs, page-level navigation, forms, and core actions are designed to remain usable without a mouse.
ACCESSIBILITY
MODLAN is building accessibility into the public platform as an engineering requirement. Accessibility is reviewed alongside security, responsiveness, performance, and content quality throughout the V125 cloud-cutover runway.
CURRENT PRACTICES
These practices are built into shared components so improvements can propagate across the site rather than being repaired page by page.
Primary navigation, dialogs, page-level navigation, forms, and core actions are designed to remain usable without a mouse.
Interactive controls receive a high-contrast focus indicator so keyboard users can identify the current control.
Decorative motion and smooth scrolling are reduced when the operating system requests reduced motion.
Long-page navigation, menus, forms, and control surfaces adapt for touch and narrow viewports instead of simply shrinking desktop UI.
Public pages use headings, landmarks, labels, named navigation regions, and status messaging intended to support assistive technology.
The interface includes additional treatment for high-contrast and forced-color environments while preserving understandable control states.
ONGOING REVIEW
Automated checks help identify structural regressions, but production accessibility also requires browser, keyboard, zoom, contrast, screen-reader, and real-device review. Findings are tracked as launch work rather than converted into unsupported compliance claims.
REPORT A BARRIER
If you encounter an accessibility barrier on the public MODLAN website, contact us with the page, feature, and problem you experienced. Do not include claim files, medical records, credentials, Social Security numbers, or sensitive evidence.