Blind and low-vision (BLV) developers create highly accessible websites. They build with screen readers, test with screen readers, and understand the user experience of assistive technology from the inside. Their sites have proper heading structure, meaningful alt-text, and logical tab order — because these are the features they use to navigate their own work.
But DesignChecker research (arXiv:2407.17681) reveals a gap: BLV developers struggle with visual properties they cannot perceive — illegible text contrast, misaligned elements, clashing colors. The sites are functionally accessible but visually rough. The developers know the semantic structure is correct but cannot verify the visual presentation.
This creates a mirror-image accessibility problem. Sighted developers build visually polished sites with poor accessibility. Blind developers build structurally sound sites with visual deficiencies. Each group excels at what they can perceive and fails at what they can't.
DesignChecker addresses this by providing non-visual feedback about visual properties — announcing contrast ratios, alignment deviations, and color harmony scores through the screen reader. The tool translates visual design dimensions into accessible information, giving BLV developers the same design feedback that sighted developers get from looking at the screen.
The broader insight: expertise is perceptually bounded. A developer who has never seen their site will miss visual issues. A developer who has never used a screen reader will miss structural issues. The fix in both cases is the same: tools that translate between perceptual modalities, giving each developer access to the feedback they're missing.
This suggests that the best-designed websites would emerge from collaboration between sighted and BLV developers — each catching what the other misses. Accessibility isn't a feature to add; it's a perspective to include.