No such column error lacks accessibility context for screen reader users

Accessibility Gap in Query Error Messaging

ClickHouse returns a 'No such column' error when column names contain mixed case and default case sensitivity is enabled, requiring exact identifier matching. This error message does not provide sufficient context for users relying on screen readers, as it lacks descriptive guidance about the specific nature of the accessibility barrier encountered.

The default query parser does not provide detailed accessibility context in error messages for screen reader users. When a column reference fails due to case sensitivity mismatches, the error output contains minimal information about why the lookup failed or how to correct the identifier format.

Additionally, column aliases with special characters require explicit quoting which may not be intuitive for all users, compounding the accessibility challenges when constructing queries with complex identifiers.

Specific Questions

• Should ClickHouse implement enhanced error message formatting that includes accessibility metadata for screen reader compatibility?
• Would adding configurable error verbosity levels help accommodate different accessibility needs without modifying core parsing behavior?
• How might the query parser be extended to provide more descriptive guidance when case sensitivity causes identifier resolution failures?