ACCESSIBILITY
PROGRESS THAT LEAVES PEOPLE OUT ISN'T PROGRESS.
At MCBC, we build technology to move things forward.
That only works if more people can actually use it.
We are committed to making the digital experiences across MCBC.IO™, MCBC.AI™, MCBC.ONE™, and other MCBC-operated websites as accessible and inclusive as reasonably possible, regardless of ability, device, or how someone interacts with technology.
Accessibility is not something we want to bolt on at the end.
IT BELONGS IN THE BUILD.
WHAT ACCESSIBILITY MEANS TO US
People experience the web differently.
Some navigate with a keyboard.
Some use screen readers.
Some magnify content.
Some need captions.
Some reduce motion.
Some need stronger contrast, clearer language, larger text, or simply more time.
Good technology should account for those differences instead of assuming everyone experiences a screen the same way.
Our goal is straightforward:
BUILD FOR MORE PEOPLE, NOT JUST MORE DEVICES.
THE STANDARD WE AIM FOR
MCBC aims to align its digital experiences with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, where reasonably applicable.
We treat accessibility as an ongoing engineering objective rather than a one-time certification exercise.
As our websites, technologies, content, and experiences evolve, we intend to continue reviewing and improving accessibility alongside them.
ACCESSIBILITY IS A PROCESS, NOT A BADGE.
WHAT WE'RE WORKING ON
Across MCBC digital experiences, we aim to consider areas including:
-
Clear heading and content structure
-
Keyboard navigation
-
Visible keyboard focus
-
Appropriate text contrast
-
Readable typography
-
Text resizing and browser zoom
-
Alternative text for meaningful images
-
Appropriate treatment of decorative graphics
-
Labels and instructions for forms
-
Understandable validation and error messages
-
Semantic page structure
-
Descriptive links and controls
-
Responsive layouts
-
Mobile accessibility
-
Accessible appointment and contact experiences
-
Motion and animation considerations
-
Reduced-motion preferences where technically supported
-
Content that does not depend exclusively on color
-
Compatibility with commonly used assistive technologies where reasonably possible
We will keep learning because accessibility, like technology itself, does not stand still.
BETTER ACCESS IS BETTER ENGINEERING.
MOTION, ANIMATION & VISUAL EXPERIMENTATION
We like experimenting with visual design.
Quite a lot, actually.
Some MCBC experiences may use abstract artwork, motion, transitions, scrolling effects, interactive elements, or other visual experimentation.
But interesting design should not require someone to tolerate an uncomfortable experience.
As the site evolves, we aim to consider accessibility requirements around motion, flashing content, readability, interaction, and user preferences such as reduced motion.
Where decorative visual effects do not provide meaningful information, they should not become a barrier to accessing the content that does.
EXPERIMENT BOLDLY. DESIGN RESPONSIBLY.
KNOWN LIMITATIONS
We're building and improving these experiences continuously, and some areas may not yet work perfectly for every user or assistive technology.
Potential limitations may arise from:
-
Third-party components
-
Scheduling or booking tools
-
Embedded external services
-
Legacy content
-
Experimental interactive experiences
-
Certain animations or visual effects
-
Features provided by external platforms
Where a third-party provider controls a component, we may have limited ability to modify its underlying accessibility implementation.
That does not mean we stop caring about the problem.
Where we identify an accessibility issue that we can reasonably address, we aim to investigate and improve it.
KNOWN PROBLEM > HIDDEN PROBLEM.
THIRD-PARTY TECHNOLOGY
Our websites may use external platforms and services for functions such as:
-
Website infrastructure
-
Forms
-
Appointment scheduling
-
Calendar integration
-
Video conferencing
-
Analytics
-
Embedded content
-
Other business services
Those services may have accessibility characteristics and limitations outside MCBC's direct control.
We still try to choose technology with usability and accessibility in mind, because outsourcing a component does not make the experience less important.
THE STACK MAY BE SHARED. THE EXPERIENCE IS STILL OUR CONCERN.
FOUND SOMETHING WE MISSED?
Good.
Tell us.
If something on an MCBC website is difficult to access, navigate, understand, or use, we want to know about it.
You can contact us at:
MCBC PRIVATE LIMITED
Email: info@mcbc.io
Location: Bangalore, Karnataka, India
Web: MCBC.IO
When reporting an accessibility problem, it helps if you can tell us:
-
Which page or feature caused the issue
-
What you were trying to do
-
The browser or device you were using
-
The assistive technology involved, if applicable
-
What happened
You do not need to provide information that is not relevant to the issue.
We will aim to review accessibility feedback and determine what we can reasonably do to improve the experience.
IF SOMETHING GETS IN THE WAY, LET US KNOW.
CONTINUOUS IMPROVEMENT
Standards evolve.
Browsers evolve.
Assistive technologies evolve.
Our websites evolve.
So accessibility work has to evolve too.
We may periodically review this statement as our technologies, design systems, accessibility practices, and applicable requirements change.
BUILT FOR PEOPLE.
Not hypothetical users.
Not perfect devices.
Not one way of experiencing the internet.
Real people. Different people. More people.
That's the direction we're building toward.