When a designer is faced with the challenge of designing to meet WCAG standards, the toolkit at their disposal is often hugely reduced. There are restrictions around using typography, colour and composition – the core fundamentals of design. Essentially, we must remember why creativity and good design is important. This quote summarises the point perfectly. “What’s the use in being legible, when nothing inspires you to take notice of it?”- Wolfgang Weingart When we remember that engagement is often the aim of design and marketing, we remember that all people - including those with impairments - enjoy visually and linguistically engaging content.

You don't compromise on accessibility. Legal implications are now driving this more than moral. Put yourself into the shows of your impaired or disabled users and you will quickly understand why I did say this.

"If everyone can’t use it, does the feature really matter?" I prioritize accessibility as a foundation, ensuring inclusivity for all users. Then, I plan feature additions that complement rather than compete with this goal. Striking this balance isn’t just about development—it’s about responsibility. Developers often face this dilemma: chase shiny new features or fix accessibility gaps? Here’s the hidden truth many overlook—new features bring users in, but accessibility keeps them loyal. The problem? It’s easy to prioritize what’s visible over what’s essential. Here’s my approach: Accessibility first: If a feature excludes users, its value diminishes.

Ah, the classic developer dilemma: shiny new features or making the app usable for everyone? Here's the trick—do both, but smartly. Plan sprints where you alternate between building cool stuff and fixing what’s broken for users with different needs. Bonus points if you bake accessibility into your new features from the start (future-you will thank you). Remember, an app nobody can use is as good as no app at all. So prioritize like a pro, listen to your users, and keep it fun—because nothing’s funnier than a flashy feature that crashes due to an unlabeled button.

To balance new features and accessibility, I prioritize user feedback to align updates with actual needs. Impact analysis ensures changes benefit all users, especially underserved groups. Iterative design helps release small, tested updates, fostering improvement in both features and accessibility without overloading resources.

To ensure that new features benefit all users, consider these strategies: Incorporate Accessibility from the Start: 1. Make accessibility a core principle during design and development. 2. Prioritize features that enhance user experience for everyone. 3. Use clear, concise language and sufficient color contrast. 4. Provide alternative text for images and videos. Test with Users with Disabilities: 1. Involve users with disabilities in the testing process. Use automated testing tools to identify potential issues. Continuous Improvement: 1. Stay updated on accessibility best practices and guidelines. 1. Conduct regular accessibility audits. 2. Train developers and designers on accessibility principles.

Balancing new features and accessibility is about impact and inclusivity. Prioritize based on user feedback and assess which option benefits the most users. Use iterative updates to address both needs, ensuring enhancements serve a diverse audience while staying aligned with your core goals.

Here's how to strike the right balance: Evaluate the impact of each new feature and accessibility improvement. What benefits users the most? Gather input from diverse users to understand their priorities. Implement changes in phases, alternating between features and accessibility enhancements. Whenever possible, integrate accessibility improvements into new features. Make sure core functionalities are accessible before adding new features. Plan and communicate your strategy, showing commitment to both innovation and inclusivity. Ensure you have dedicated resources for both development and accessibility. Finding the right balance ensures a better experience for all users!

To balance new features and accessibility, prioritize accessibility from the start, use testing tools, follow WCAG guidelines, make incremental improvements, collaborate with the team, involve diverse users in testing, and stay updated on accessibility best practices. Remember, accessibility is an ongoing process, not a one-time fix.

Accessibility should be an integral part of the development process starting from the beginning. Accessibility considerations should be incorporated into the design from the start. It includes creating proper accessibility wireframes, mockups and prototypes. Accessibility should be integrated into the reusable UI components. It should be measurable and it should exist clear guidance and standards which are understood and constantly followed by the team.