Accessibility of sgcUI

Every sgcUI product exposes its content to Microsoft UI Automation, the API that screen readers such as Narrator and NVDA use, can be operated with the keyboard, with the exceptions listed under known limitations, and follows the Windows high contrast themes. This page states what we commit to, what is covered, what is not covered yet, and links the conformance report of each platform.

Our Commitment

eSeGeCe builds sgcUI so that the applications made with it can be used by everyone, including people who use a screen reader, people who use only the keyboard and people who need strong contrast. The accessibility support is part of every product and every edition, the free Community edition included, and it is on by default: drop a control on a form and it is accessible, with no setup and no extra cost while no accessibility client is running.

The support is designed to meet the requirements of EN 301 549 and of WCAG 2.1 level AA that apply to software components: name, role, value and state of every element, keyboard operation, visible focus, non text contrast, and the use of the system colours. We publish an accessibility conformance report for each platform and update it when the components change.

The final conformance of your application also depends on how you use the components: give every control a meaningful name, keep a logical tab order on your forms, and do not convey information by colour alone in the data you show.

What Is Covered

sgcGrid, sgcPivotGrid, sgcCharts, sgcGauges, sgcDashboard, sgcPlanner, sgcDiagram, sgcWizard, sgcNavigation, sgcToolbar, sgcEditors and sgcMaps.

The components expose their content to Microsoft UI Automation, the accessibility interface of Windows that screen readers such as Narrator and NVDA and the testing tools of Microsoft use: a grid is exposed as a table with rows, cells and headers, a chart as a list of series and points, a planner as a list of items, and so on. Older clients that only speak MSAA are served through the bridge Windows provides between UI Automation and MSAA.

  • VCL: UI Automation in every supported Delphi and C++Builder version, from Delphi 7 to Delphi 13 and from C++Builder 2007 to C++Builder 13, with one code path and the same behaviour in every version.
  • FireMonkey: UI Automation on Windows. The form is the root and every sgcUI control of the form is an element inside it.
  • WinForms: every control serves its own UI Automation provider, so a grid is a table with the Grid and Table patterns. .NET Framework 4.7.2 and .NET 8, 9 and 10.
  • WPF: every control returns an automation peer and one peer per item it draws. .NET Framework 4.7.2 and .NET 8, 9 and 10.
  • Avalonia 12 (12.0 or later, tested with 12.1.4): every control returns an automation peer and one peer per item it draws, passed to UI Automation on Windows. .NET 8, 9 and 10.
  • sgcMaps is accessible on VCL, on FireMonkey on Windows and on WinForms, the platforms where it is available.
  • Keyboard: keyboard alternatives for moving and resizing tiles, planner items and shapes, moving Kanban cards, creating Gantt dependencies and diagram links, adding shapes from the palette, and moving pivot fields and grid columns. Every interactive control shows a visible focus ring.
  • Windows high contrast is followed automatically while a control uses the default theme, and the utHighContrast theme forces it. Right to left layouts and high DPI are supported.

Not covered

  • The sgcPDF viewer control and the sgcReports preview control do not expose accessibility information in this release. The PDF files that sgcPDF and sgcReports produce can be tagged PDF/UA documents, which is a document feature and is not evaluated in the reports.
  • FireMonkey on macOS, iOS and Android: the accessibility layer is available on Windows only for now.
  • Avalonia was evaluated on Windows only. Other operating systems were not evaluated.

Conformance Status

The conformance reports follow the international edition of VPAT 2.5 and cover WCAG 2.1 level A and AA, the Revised Section 508 standards and EN 301 549 V3.2.1 (2021-03). Most criteria are supported, some are partially supported, and the remarks of each row say what the components provide and what is the responsibility of the application developer.

The reports are based on a review of the implementation against its design, product by product, on automated in process tests in the product QA suites (names, roles, values, states, patterns, element trees, bounds under right to left layouts and at 100 to 200 percent DPI, keyboard alternatives, focus indicator, high contrast rendering and the zero cost rule when no client listens), and on the measured contrast of the theme colours.

We tested the components with the NVDA 2026.2 screen reader on all platforms (Delphi VCL, C++Builder, FireMonkey on Windows, .NET WinForms, WPF and Avalonia). We also scanned them with Accessibility Insights for Windows and AxeWindows 2.4.2 and fixed all real defects found. Narrator was not tested. The conformance reports state the result for each criterion.

Known Limitations

As stated in the conformance reports.

  • No keyboard alternative yet for sgcGrid column width resizing, sgcCharts zoom and pan by mouse and the financial drawing tools, and sgcDiagram connector bend points. Applications can offer these through the component API.
  • Default themes: component borders are 1.5:1 (light), grid lines 1.2:1 (light) and 1.3:1 (dark), four of the eight light series colours are below 3:1 on white, and the light accent colour is 4.4:1 on white where a product uses it for text. The high contrast theme meets the contrast criteria, and the developer can choose the colours.
  • In the default light and dark themes, chart series, planner categories and grid format rules are told apart by colour unless the developer adds markers, dash patterns, data labels or text. The same information is always exposed as text to assistive technology.
  • Chart tooltips and crosshair labels follow the pointer or the focused point and cannot be hovered. Their value is also exposed as the value of the focused point.
  • The UI Automation Text pattern (text attributes, caret and selection inside editors and diagram labels) is not implemented. Text is exposed as names and values, and the VCL text editors embed a native edit control that exposes its own text.
  • No LabeledBy relationship to a separate label control is exposed. Set the accessible name of the control instead.
  • The system text size setting is applied only when the application maps it to the fonts of the components.
  • sgcMaps: the map image is described by its centre and zoom only, and the map renderer does not follow high contrast, because the map image is tile imagery from the provider.
  • The alternative text of the print and PDF export comes from the same generator as the default accessible description. An accessible description set by the application is not used by the export.
  • Avalonia 12 has no Grid and Table patterns, so sgcGrid and sgcPivotGrid give the column header and the position in the name and help text of each cell instead of a table relationship. Two more Avalonia limits were found with NVDA. With the default (selective) UI Automation event registration of NVDA, state changes of items inside sgcUI controls are not announced, because the Avalonia window answers GetFocusedElement with the control and not with the item. Avalonia also has no UI Automation notification event, so live notifications are not announced by Avalonia. Workaround: in NVDA open Settings, Advanced, and set "Registration for UI Automation events and property changes" to Global. State changes of items are then announced; live notifications are not.
  • The help is published as HTML pages, CHM and PDF with headings and text alternatives, and has not been audited against WCAG 2.1 AA.

Accessibility Conformance Reports

One report per platform, VPAT 2.5 international edition, October 2026. Read it as a web page or download the PDF.

ReportPlatformWeb pagePDF
sgcUI for Delphi VCLDelphi 7 to Delphi 13 and C++Builder 2007 to C++Builder 13, VCL applications on Windows (Win32 and Win64).Read the reportDownload PDF
sgcUI for Delphi FireMonkey (Windows)Delphi FireMonkey applications on Windows (Win32 and Win64). FireMonkey on macOS, iOS and Android is not covered.Read the reportDownload PDF
sgcUI for .NET WinForms.NET WinForms applications on Windows: .NET Framework 4.7.2 and later, .NET 8, .NET 9 and .NET 10.Read the reportDownload PDF
sgcUI for .NET WPF.NET WPF applications on Windows: .NET Framework 4.7.2 and later, .NET 8, .NET 9 and .NET 10.Read the reportDownload PDF
sgcUI for .NET AvaloniaAvalonia 12 applications on .NET 8 or later, evaluated on Windows.Read the reportDownload PDF

Contact Us

If a control is hard to use with your screen reader, your keyboard or your contrast settings, or if you need a report in another format, write to info@esegece.com. Tell us the product, the platform, the version and the assistive technology you use, and we will look into it.

This statement was prepared in October 2026 for sgcUI 2026.10. The Avalonia results were tested again with Avalonia 12.1.4 on 12 October 2026.

Read the accessibility help topic

Best value: All-AccessEvery eSeGeCe product, Premium Support included, from €1,059/year.
See All-Access pricing