Skip to content

docs: update readme for Q4 2021 #23898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 4, 2021
Merged

docs: update readme for Q4 2021 #23898

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,20 +33,20 @@ If you'd like to contribute, please follow our [contributing guidelines][contrib
our [`help wanted`][help-wanted] label for a list of issues with good opportunities for
contribution.

## What we're working on now (Q2 2021):
## What we're working on now (Q4 2021):
* Continuing to create new, API-compatible versions of the Angular Material components backed by
[MDC Web][] ([see @jelbourn's ng-conf talk](https://youtu.be/4EXQKP-Sihw?t=891)). Much of our effort
is dedicated towards rolling out these new versions of the components across Angular apps
inside Google. This work will payoff with the following benefits:
inside Google. This work will pay off with the following benefits:
* Dramatically improve consistency with the Material Design spec, which has changed significantly
since Angular Material's 2016 inception.
since Angular Material's 2016 inception. This also makes future versions of Material Design
significantly easier to adopt.
* Introduce a new theming API for component density, a top feature request.
* Fix a number of longstanding accessibility bugs.
* Increase number of people working to continuously improve the components on an on-going basis
* Increase number of people working to continuously improve the components on an ongoing basis
(both the Angular team and the Material Design team).
* Continue work on virtual-scroll support for cdk/table.
* Accessibility - we'll be doing a major pass on outstanding accessibility issues and reviewing all
of the components for accessibility best practices such as WCAG.
* Accessibility - we'll be focusing on improving the accessibility of `MatDatepicker` as well as
evaluating accessibility bugs for mobile web platforms.


## About the team
Expand Down