Skip to main content

Accessibility

FDC controls participate in Flutter's focus, keyboard, and semantics systems. Application accessibility still depends on how grids, editors, validation messages, dialogs, and surrounding navigation are composed.

Preserve keyboard workflows​

The data grid supports keyboard navigation and editing. Do not wrap the grid in custom key handlers that consume navigation keys before the grid receives them unless that behavior is intentional.

See Keyboard Navigation.

Use meaningful labels​

Choose concise, descriptive column labels and editor labels. Avoid abbreviations that only make sense to the development team.

FdcTextColumn(
  fieldName: 'company',
  label: 'Company',
)

Expose validation clearly​

Validation should not rely on color alone. Keep validation messages specific and actionable, and ensure application-level dialogs or notices can be reached and dismissed with the keyboard.

Maintain readable contrast​

When customizing themes, verify text, focus indicators, selection states, disabled states, and validation states under the actual application color scheme.

Test the complete screen​

Accessibility should be tested in the composed application, not only at the component level. Verify:

  • keyboard-only navigation;
  • visible focus movement;
  • edit entry and exit;
  • validation feedback;
  • dialogs opened from lookup actions;
  • screen-reader reading order and labels;
  • text scaling and constrained layouts.