New home page (#1)

content/_index.md

@@ -9,14 +9,33 @@ section_path = "blog/_index.md"
 max_posts = 5
 +++
 
-# A True Universal Access Solution
+## Accessibility infrastructure for UI toolkits
 
-Consumers and developers alike have had to deal with the complications brought about by separate, disparate accessibility standards. Windows with MSAA and UI Automation, Mac OS with CocoaNSAccessibility, Linux with AT-SPI, you name it. This doubles – sometimes even triples – the workload for developers striving for unparalleled access across platforms. Historically, cross-platform toolkits that end up integrating accessibility hit Windows first before they do Mac and/or Linux. This could be for a number of reasons – larger market-share, more documentation, budget/time constraints, etc. But regardless, users are left behind.
+AccessKit makes it easier to implement accessibility, for screen readers and other assistive technologies, in toolkits that render their own user interface elements. It provides a cross-platform, cross-language abstraction over accessibility APIs, so toolkit developers only have to implement accessibility once.
 
-Not anymore. AccessKit enables developers to do their accessibility implementation once in order to make it accessible for nearly all use cases. At last, developers can spend less time working their way through the complications of the various accessibility implementations and more time fine-tuning their user interface to provide the best in accessibility for assistive technology across the board.
+## Getting started
 
-## Attainable. Efficient. Cross-platform
+AccessKit is written in Rust and has bindings for C and Python.
 
-AccessKit respects your time and budget by taking care of the platform communication aspect of accessibility. Once you key in all the pertinent accessibility information about your UI elements, AccessKit will take it from there.
+### Rust
 
-[How it works](./how-it-works/)
+The following Rust projects already integrate AccessKit:
+
+* [Bevy](https://bevyengine.org/)
+* [egui](https://github.com/emilk/egui)
+* [Slint](https://slint.dev/)
+* [Xilem](https://github.com/linebender/xilem)
+
+If you are using the [winit](https://crates.io/crates/winit) cross-platform windowing library for Rust, you should use the [AccessKit winit adapter](https://crates.io/crates/accesskit_winit). Otherwise, you'll need to use one or more of the AccessKit platform adapters:
+
+* [macOS adapter](https://crates.io/crates/accesskit_macos)
+* [Unix adapter](https://crates.io/crates/accesskit_unix)
+* [Windows adapter](https://crates.io/crates/accesskit_windows)
+
+### C
+
+The latest release of the AccessKit C bindings, including the header file, pre-built libraries, examples, and source code, can be found on the [GitHub releases page for the C bindings](https://github.com/AccessKit/accesskit-c/releases).
+
+### Python
+
+You can find the [AccessKit Python bindings on PyPI](https://pypi.org/project/accesskit/).